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

userporn.pro

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

This reading of userporn.pro was taken 3d ago

userporn.pro is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting userporn.pro 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 userporn.pro 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
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-04 19:44 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 userporn.pro actually stands on - every host below is a signed observation
userporn.pro
A / AAAA
162.244.32.72
unattributedserves the site
NS
ns1.userporn.prons2.userporn.pro
userporn.proanswers its DNS
TLS
userporn.pro
Let's Encryptissued its certificate

DNS Records

A 1

  • 162.244.32.72

TXT 1

  • v=spf1 -all

NS 2

  • ns1.userporn.pro
  • ns2.userporn.pro

SOA 1

  • ns1.userporn.pro admin.userporn.pro

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

Common NameIssuerExpires
userporn.pro C=US, O=Let's Encrypt, CN=YE2 Mon, 31 Aug 2026 12:26:47 +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_345fcfcf061ad849
Output Hash
d7cba44b9dc69db4aa65d61e1dd074b770f978f194132a1d5bbf79c030fb9167
Signature
ed25519:6048e289cbde415d9068363f5b05ede9cd6a5360fb518bd2e11fc55513613e44fa295c853b196b83ccc6b01dbd03a4d6d3cb303e85e24a8efa2b221e38a14a02
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser