CONTINUOUS INTERNET TELEMETRY24H DRIFT4,871 material changesacross 4,498 domains · 24h to ~2h ago · -3,892 vs yesterdayNOW560 curated domains not reachablelast probe, steadySITE ERRORS34,304 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,289 sites429 rate-limit / 403 bot-block, a posture signalMOVERokta.comNo mail routes in the latest observation

yoav.blog

Observed Aug 2, 2026, 22:06 UTC (7h ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.

Verify this receipt yourself + Watch this domain
Up right now
Secured byLet's Encrypt
IPv6 · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 22:06 UTC

DomainDrift asked this domain for a TXT record at a name nobody registers, and got an answer back. A domain that answers a name that was never created is answering names in general, and that is wildcard DNS.

Wildcard DNS clusters around domain parking, dynamic DNS and catch-all hosting. It is also a real attack surface: if every invented hostname resolves, then a hostname an attacker invents resolves too, which is the ground state for subdomain takeover and for phishing hosted under a name that looks legitimate.

This is evidence of wildcard behaviour, not a proven fact. It rests on one control name: a domain could legitimately serve a TXT record at exactly that name for an unrelated reason, and a wildcard that answers address records but not TXT records would not be caught here at all. What this reading is and is not.

INFRASTRUCTURE MAPwhat yoav.blog actually stands on - every host below is a signed observation
yoav.blog
A / AAAA
185.199.109.153185.199.110.153185.199.111.153185.199.108.153+4 more
2606serves the site
NS
ns2.wordpress.comns3.wordpress.comns1.wordpress.com
wordpress.comanswers its DNS
TLS
yoav.blog
Let's Encryptissued its certificate

DNS Records

A 4

  • 185.199.109.153
  • 185.199.110.153
  • 185.199.111.153
  • 185.199.108.153

AAAA 4

  • 2606:50c0:8000::153
  • 2606:50c0:8003::153
  • 2606:50c0:8002::153
  • 2606:50c0:8001::153

TXT 1

  • v=spf1 include:_spf.wpcloud.com ~all

NS 3

  • ns2.wordpress.com
  • ns3.wordpress.com
  • ns1.wordpress.com

SOA 1

  • ns1.wordpress.com hostmaster.wordpress.com

MCP_RECORDS 1

  • v=spf1 include:_spf.wpcloud.com ~all

DMARC_RECORDS 1

  • v=DMARC1;p=none;

BIMI_RECORDS 1

  • v=spf1 include:_spf.wpcloud.com ~all

MTA_STS_RECORDS 1

  • v=spf1 include:_spf.wpcloud.com ~all

TLS Certificates (3)

Common NameIssuerExpires
yoav.blog C=US, O=Let's Encrypt, CN=YR1 Sat, 24 Oct 2026 22:17:51 +0000
YR1 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000
Root YR C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (0)

None observed.

The proof

Signed at scan time. Check the math yourself. Every line above is part of one signed observation. Re-hash it and check the Ed25519 signature in your own browser; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_d1a7eaea6716e35f
Output Hash
b24ea41a579c3e6e98c9c4fbe7d9c776ca1f2e984af2a555e557700818f527a0
Signature
ed25519:06c4c1a59ef0bc67b06b19afc3dfe9445ea436bbc94987a3a3c097166fd36dbecffe3d092357d9d182548fb0d6a257179dfc6cc067ce475a874c3164c7e3ee0f
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser