CONTINUOUS INTERNET TELEMETRY24H DRIFT13,565 material changesacross 13,085 domains · 24h to ~60m ago · -27,295 vs yesterdayNOW559 curated domains not reachablelast probe, steadySITE ERRORS34,154 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,321 sites429 rate-limit / 403 bot-block, a posture signal

zerova.net

Observed Aug 2, 2026, 08:20 UTC (11h 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 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-02 08:20 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 zerova.net actually stands on - every host below is a signed observation
zerova.net
A / AAAA
147.135.37.231
unattributedserves the site
NS
dns1.zerova.netdns2.zerova.net
zerova.netanswers its DNS
MX
mx1.zerova.netmx2.zerova.net
zerova.netreceives its email
TLS
zerova.net
Let's Encryptissued its certificate

DNS Records

A 1

  • 147.135.37.231

MX 2

  • 10mx1.zerova.net
  • 20mx2.zerova.net

TXT 1

  • v=spf1 a mx ip4:147.135.37.231 a:zerova.net ~all

NS 2

  • dns1.zerova.net
  • dns2.zerova.net

SOA 1

  • dns1.zerova.net dns.zerova.com

SRV 3

  • mail.zerova.net:443 p10
  • imap.zerova.net:993 p10
  • mail.zerova.net:587 p20

MCP_RECORDS 1

  • v=spf1 a mx ip4:147.135.37.231 a:zerova.net ~all

DMARC_RECORDS 1

  • v=DMARC1; p=reject; rua=mailto:dmarc-rua@zerova.net; ruf=mailto:dmarc-ruf@zerova.net; adkim=s; aspf=s

BIMI_RECORDS 1

  • v=spf1 a mx ip4:147.135.37.231 a:zerova.net ~all

MTA_STS_RECORDS 1

  • v=spf1 a mx ip4:147.135.37.231 a:zerova.net ~all

TLS Certificates (3)

Common NameIssuerExpires
zerova.net C=US, O=Let's Encrypt, CN=YR2 Wed, 28 Oct 2026 02:05:04 +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 (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; nothing leaves your machine.

Verify this receipt

Put the receipt on your own site. A live badge showing what DomainDrift observes and signs for zerova.net. It updates itself. It attests a signed observation - not that the site is safe.

DomainDrift signed-observation badge for zerova.net <a href="https://domaindrift.io/t/zerova.net"> <img src="https://domaindrift.io/badge/zerova.net.svg" width="300" height="64" alt="DomainDrift signed observations for zerova.net"> </a>

Ed25519 Receipt

Receipt ID
rcpt_e0bf0026c678388f
Output Hash
989230338057be2f5e6966812d4763ebbcf96451fc40b8a1cec0114109333bf0
Signature
ed25519:a44382b782428eaa07a902f358362eb4fd36a3e0deb490b548aa5adbe22d499419c9b6b1223be0fb543518270a849ea993d04e5dff3f8946b9ecaaf28b969e09
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser