CONTINUOUS INTERNET TELEMETRY24H DRIFT68,088 material changesacross 64,935 domains · 24h to ~2h ago · +33,471 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW538 curated domains not reachablelast probe, steadySITE ERRORS33,857 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 123,111 sites429 rate-limit / 403 bot-block, a posture signal

edesaulniers.com

Observed Aug 3, 2026, 00:17 UTC (3d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of edesaulniers.com was taken 3d ago

edesaulniers.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting edesaulniers.com under watch moves it to the fast lane, where DomainDrift re-checks it about every 5 minutes and signs each reading, so a change becomes a dated event within minutes instead of waiting for the sweep to come round.

Watch edesaulniers.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 12:27 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 edesaulniers.com actually stands on - every host below is a signed observation
edesaulniers.com
A / AAAA
34.111.179.208
unattributedserves the site
NS
ns3.wordpress.comns1.wordpress.comns2.wordpress.com
wordpress.comanswers its DNS
TLS
edesaulniers.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 34.111.179.208

TXT 1

  • replit-verify=aa3574bf-00c0-46e1-9ad7-dda592792388

NS 3

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

SOA 1

  • ns1.wordpress.com hostmaster.wordpress.com

MCP_RECORDS 1

  • replit-verify=aa3574bf-00c0-46e1-9ad7-dda592792388

DMARC_RECORDS 1

  • replit-verify=aa3574bf-00c0-46e1-9ad7-dda592792388

BIMI_RECORDS 1

  • replit-verify=aa3574bf-00c0-46e1-9ad7-dda592792388

MTA_STS_RECORDS 1

  • replit-verify=aa3574bf-00c0-46e1-9ad7-dda592792388

TLS Certificates (4)

Common NameIssuerExpires
edesaulniers.com C=US, O=Let's Encrypt, CN=YE2 Mon, 05 Oct 2026 03:45:19 +0000
YE2 C=US, O=ISRG, CN=Root YE Sat, 02 Sep 2028 23:59:59 +0000
Root YE C=US, O=Internet Security Research Group, CN=ISRG Root X2 Thu, 02 Sep 2032 23:59:59 +0000
ISRG Root X2 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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_533c180a169c5059
Output Hash
c7303e2ea351859eca2eebda20bb55b9f9ad1ab5f76e041e2714252ae508e3c4
Signature
ed25519:f3375544d8bbaf70391efb45e49ed3aad88c3400bf21ef00c5a93616d312e251eeb4a4c88b165d3f33e578b486e3746d4c3735b0190bd5578d221ad68ce72a0b
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser