CONTINUOUS INTERNET TELEMETRY24H DRIFT12,660 material changesacross 11,816 domains · last 24h · +3,897 vs yesterdayNOW560 curated domains not reachablelast probe, steadySITE ERRORS34,304 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,289 sites429 rate-limit / 403 bot-block, a posture signalMOVERokta.comNo mail routes in the latest observation

upornia.net

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

This reading of upornia.net was taken 1d ago

upornia.net is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting upornia.net 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 upornia.net Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Email byGoogle Workspace
Secured byLet's Encrypt
2 subdomains · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 08:55 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 upornia.net actually stands on - every host below is a signed observation
upornia.net
A / AAAA
109.206.176.116
unattributedserves the site
NS
dolly.ns.cloudflare.comtroy.ns.cloudflare.com
cloudflare.comanswers its DNS
MX
aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comalt1.aspmx.l.google.com+1 more
Google Workspacereceives its email
TLS
direct.upornia.net
Let's Encryptissued its certificate

DNS Records

A 1

  • 109.206.176.116

MX 5

  • 1aspmx.l.google.com
  • 10alt3.aspmx.l.google.com
  • 10alt4.aspmx.l.google.com
  • 5alt1.aspmx.l.google.com
  • 5alt2.aspmx.l.google.com

TXT 1

  • v=spf1 include:_spf.google.com -all

NS 2

  • dolly.ns.cloudflare.com
  • troy.ns.cloudflare.com

SOA 1

  • dolly.ns.cloudflare.com dns.cloudflare.com

MCP_RECORDS 1

  • v=spf1 include:_spf.google.com -all

DMARC_RECORDS 1

  • v=spf1 include:_spf.google.com -all

BIMI_RECORDS 1

  • v=spf1 include:_spf.google.com -all

MTA_STS_RECORDS 1

  • v=spf1 include:_spf.google.com -all

TLS Certificates (3)

Common NameIssuerExpires
direct.upornia.net C=US, O=Let's Encrypt, CN=YR2 Sun, 11 Oct 2026 03:08:33 +0000
YR2 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000
Root YR C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (2)

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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_1144b6616b672786
Output Hash
6b90451da61000d6c65eb94eae4768699f639ca2105bd1d532b899026c24c39b
Signature
ed25519:2738f9309803f1ef1e4ef22b9b4eb453a154f66466f839c30e9c77b17d822295d757bc0196649ac0fb9e29e4b2db61b7b9d1022c0868f0abed86c83211d84d0d
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser