CONTINUOUS INTERNET TELEMETRY24H DRIFT48,392 material changesacross 43,424 domains · 24h to ~60m ago · +13,986 vs yesterdayROTATION55 domains moved DNS from koaladns.com to magpiedns.com, 54 moved backa rotation loop, not a migration · 24hNOW611 curated domains not reachablelast probe, steadySITE ERRORS34,178 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,838 sites429 rate-limit / 403 bot-block, a posture signal

rishikeshcity.com

Observed Aug 9, 2026, 18:24 UTC (4h 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.

Up right now
Secured byGoogle Trust Services
1 subdomain · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-09 18:24 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 rishikeshcity.com actually stands on - every host below is a signed observation
rishikeshcity.com
A / AAAA
192.0.78.151192.0.78.222
unattributedserves the site
NS
ns3.wordpress.comns1.wordpress.comns2.wordpress.com
wordpress.comanswers its DNS
TLS
tls.automattic.com
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 192.0.78.151
  • 192.0.78.222

TXT 1

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

NS 3

  • ns3.wordpress.com
  • ns1.wordpress.com
  • ns2.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
tls.automattic.com C=US, O=Google Trust Services, CN=WR1 Fri, 23 Oct 2026 19:19:15 +0000
WR1 C=US, O=Google Trust Services LLC, CN=GTS Root R1 Tue, 20 Feb 2029 14:00:00 +0000
GTS Root R1 C=BE, O=GlobalSign nv-sa, 2.5.4.11=Root CA, CN=GlobalSign Root CA Fri, 28 Jan 2028 00:00:42 +0000

Subdomains (1)

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_7f8dd708e1410858
Output Hash
a0b94dc74e32f17a38687c8beced596505a60dc85562b88002c47deb33bb8faa
Signature
ed25519:17be2a0f867d5064633b2ec6e43330894e49aff8a333ce0376235b5bfb3ed9b55f5b88b4bc05988e1162cd631210b17f6d905d949b472e5b571498f3a754da04
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser