CONTINUOUS INTERNET TELEMETRY24H DRIFT68,088 material changesacross 64,935 domains · 24h to ~2h ago · +33,471 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.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

wt-safetag.com

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

This reading of wt-safetag.com was taken 3d ago

wt-safetag.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting wt-safetag.com 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 wt-safetag.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Not responding
Signed observation on record.
tranco_40k
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 13:49 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 wt-safetag.com actually stands on - every host below is a signed observation
wt-safetag.com
A / AAAA
127.0.0.1
unattributedserves the site
NS
ns5.gdns.dens4.gdns.dens6.gdns.dens3.gdns.de
gdns.deanswers its DNS

DNS Records

A 1

  • 127.0.0.1

MX 1

  • 0

TXT 3

  • pcl5h4e2q89382mbocne1j25pu
  • v=spf1 -all
  • _js568orppsw3gm0ing7qq7fonn8bbfd

NS 4

  • ns5.gdns.de
  • ns4.gdns.de
  • ns6.gdns.de
  • ns3.gdns.de

SOA 1

  • ns3.gdns.de technik.leonex.de

MCP_RECORDS 1

  • pcl5h4e2q89382mbocne1j25pu

DMARC_RECORDS 1

  • v=DMARC1; p=reject; rua=mailto:dmarc-rua@shortest-route.com;

BIMI_RECORDS 1

  • pcl5h4e2q89382mbocne1j25pu

MTA_STS_RECORDS 1

  • pcl5h4e2q89382mbocne1j25pu

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_4bbb9d8bcc5aec92
Output Hash
f6f8e4e7518d9eb83882409b8b6bbd964433e0e6c1ddad5d6c29f397f5326e27
Signature
ed25519:42c54397b89d1cf4e3568cd0698c4ec3e43a3d74cf3bd3ef9067ece0b58a0f854d2a6af9f348f4829e0839bc65a197d6784eb840d1b2a238bc413d90ca426406
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser