CONTINUOUS INTERNET TELEMETRY24H DRIFT47,514 material changesacross 42,637 domains · 24h to ~2h ago · +13,108 vs yesterdayROTATION52 domains moved DNS from koaladns.com to magpiedns.com, 51 moved backa rotation loop, not a migration · 24hNOW613 curated domains not reachablelast probe, steadySITE ERRORS34,190 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,868 sites429 rate-limit / 403 bot-block, a posture signal

reachcm.com

Observed Aug 2, 2026, 09:22 UTC (7d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of reachcm.com was taken 7d ago

reachcm.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting reachcm.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 reachcm.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-09 10: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 reachcm.com actually stands on - every host below is a signed observation
reachcm.com
A / AAAA
52.153.216.100
unattributedserves the site
NS
ns-1097.awsdns-09.orgns-200.awsdns-25.comns-2037.awsdns-62.co.ukns-845.awsdns-41.net
awsdns-09.org + awsdns-25.com + moreanswers its DNS
TLS
reachlogin.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 52.153.216.100

TXT 1

  • v=spf1 -all

NS 4

  • ns-1097.awsdns-09.org
  • ns-200.awsdns-25.com
  • ns-2037.awsdns-62.co.uk
  • ns-845.awsdns-41.net

SOA 1

  • ns-2037.awsdns-62.co.uk awsdns-hostmaster.amazon.com

MCP_RECORDS 1

  • v=DKIM1; p=

DMARC_RECORDS 1

  • v=DMARC1; p=reject;rua=mailto:dmarc-reporting@reachmedianetwork.com; ruf=mailto:dmarc-reporting@reachmedianetwork.com

BIMI_RECORDS 1

  • v=DKIM1; p=

MTA_STS_RECORDS 1

  • v=DKIM1; p=

TLS Certificates (3)

Common NameIssuerExpires
reachlogin.com C=US, O=Let's Encrypt, CN=YR1 Wed, 07 Oct 2026 23:11:19 +0000
Root YR C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000
YR1 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 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_215a03475a0ae768
Output Hash
fc1242b64f85247a85c7b56b0a5c937e9c3ddf0a28696f61fd62af6a544c3e08
Signature
ed25519:cb59334d57c80d398f0c0842caf460bd697b1836e0b8d29f5a213d417bdcc067b9a13b3c085b74e317684f8e0f352e8208d34f0bd4b1940bbe7920b35ff8be01
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser