CONTINUOUS INTERNET TELEMETRY24H DRIFT50,294 material changesacross 44,212 domains · 24h to ~60m ago · +15,888 vs yesterdayROTATION59 domains moved DNS from magpiedns.com to koaladns.com, 56 moved backa rotation loop, not a migration · 24hNOW612 curated domains not reachablelast probe, steadySITE ERRORS34,081 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,120 sites429 rate-limit / 403 bot-block, a posture signal

researcha.com

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

This reading of researcha.com was taken 7d ago

researcha.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting researcha.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 researcha.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byGoDaddy.com
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-09 10:33 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 researcha.com actually stands on - every host below is a signed observation
researcha.com
A / AAAA
76.223.54.14613.248.169.48
unattributedserves the site
NS
ns1.afternic.comns2.afternic.com
afternic.comanswers its DNS
TLS
researcha.com
GoDaddy.comissued its certificate

DNS Records

A 2

  • 76.223.54.146
  • 13.248.169.48

MX 1

  • 0

TXT 1

  • v=spf1 -all

NS 2

  • ns1.afternic.com
  • ns2.afternic.com

SOA 1

  • ns1.afternic.com dns.jomax.net

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=spf1 -all

BIMI_RECORDS 1

  • v=spf1 -all

MTA_STS_RECORDS 1

  • v=spf1 -all

TLS Certificates (3)

Common NameIssuerExpires
researcha.com C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., 2.5.4.11=http://certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2 Fri, 09 Oct 2026 15:28:44 +0000
Go Daddy Secure Certificate Authority - G2 C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., CN=Go Daddy Root Certificate Authority - G2 Sat, 03 May 2031 07:00:00 +0000
Go Daddy Root Certificate Authority - G2 C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., CN=Go Daddy Root Certificate Authority - G2 Thu, 31 Dec 2037 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_7ab3c6eb13dc9694
Output Hash
d37e37b4e497af57bf1d6a52c0c79e7430d7e530618dd4c7a080c3c2b881477d
Signature
ed25519:be90212437768e34089af5edbfc033faa7fad7e41a698ec5c62f1c98b44707ff8b771dbddac76c1a0b290ff06d62acdcb01c9db757ce778a1c184d8f0afb700e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser