CONTINUOUS INTERNET TELEMETRY24H DRIFT66,120 material changesacross 63,653 domains · 24h to ~3h ago · +31,503 vs yesterdayROTATION56 domains moved DNS from magpiedns.com to koaladns.com, 56 moved backa rotation loop, not a migration · 24hNOW536 curated domains not reachablelast probe, steadySITE ERRORS33,825 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 121,690 sites429 rate-limit / 403 bot-block, a posture signal

pny.co.in

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

This reading of pny.co.in was taken 3d ago

pny.co.in is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting pny.co.in 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 pny.co.in Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Up right now
Runs onSEDO
Secured byDigiCert
push_legacy
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 13: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 pny.co.in actually stands on - every host below is a signed observation
pny.co.in
A / AAAA
64.190.63.222
SEDOserves the site
NS
ns2.sedoparking.comns1.sedoparking.com
sedoparking.comanswers its DNS
MX
localhost
localhostreceives its email
TLS
pny.co.in
DigiCertissued its certificate

DNS Records

A 1

  • 64.190.63.222

MX 1

  • 0localhost

TXT 1

  • v=spf1 -all

NS 2

  • ns2.sedoparking.com
  • ns1.sedoparking.com

SOA 1

  • ns1.sedoparking.com hostmaster.sedo.de

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 (0)

None.

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_6fe3687fbf200f33
Output Hash
b287e5758e06bd8524070d5e732f7297351cf95ef2c98fdc4d3aff6aa21872bc
Signature
ed25519:0a35d9a4b34cba7bfda43a77bf34927a606f16de55ef5715cca9d63b9918110b507003629f899cb6a268adc7921ec8dc98783e9fe44c69952e2791dcf041ea07
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser