CONTINUOUS INTERNET TELEMETRY24H DRIFT68,088 material changesacross 64,935 domains · 24h to ~2h ago · +33,471 vs yesterdayROTATION56 domains moved DNS from magpiedns.com to koaladns.com, 56 moved backa rotation loop, not a migration · 24hNOW538 curated domains not reachablelast probe, steadySITE ERRORS33,857 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 123,111 sites429 rate-limit / 403 bot-block, a posture signal

vipathai.com.au

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

This reading of vipathai.com.au was taken 3d ago

vipathai.com.au is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting vipathai.com.au 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 vipathai.com.au Watching a domain needs a DRM3 account. The reading above stays free and public either way.
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-05 14:50 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 vipathai.com.au actually stands on - every host below is a signed observation
vipathai.com.au
A / AAAA
103.224.182.244
unattributedserves the site
NS
ns3.abovedomains.comns4.abovedomains.com
abovedomains.comanswers its DNS
MX
park-mx.above.com
above.comreceives its email
TLS
zulum.cf
Let's Encryptissued its certificate

DNS Records

A 1

  • 103.224.182.244

MX 1

  • 10park-mx.above.com

TXT 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

NS 2

  • ns3.abovedomains.com
  • ns4.abovedomains.com

SOA 1

  • ns1.abovedomains.com hostmaster.trellian.com

MCP_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

MTA_STS_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

TLS Certificates (3)

Common NameIssuerExpires
zulum.cf C=US, O=Let's Encrypt, CN=YR2 Tue, 06 Oct 2026 18:49:56 +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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_568d4f5deaeb38ac
Output Hash
2140d4216a4f525296d2830a87ca07cbc36a4a7ba6d73295dd2e0a2d97e6ca03
Signature
ed25519:28c0e959f3b32cd790ae4f342116c5a6a53bd405517293d0407f0368232156753c2e8ef69e6d278792dfe6d8b003713951bb8d3f1d083c3ee69a6297121fb104
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser