CONTINUOUS INTERNET TELEMETRY24H DRIFT23,583 material changesacross 21,757 domains · 24h to ~2h agoROTATION57 domains moved DNS from koaladns.com to kirklanddc.com, 56 moved backa rotation loop, not a migration · 24hEMAIL DRIFT1 domain switched email providertop destination ~NOW605 curated domains not reachablelast probe, steadySITE ERRORS33,518 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,266 sites429 rate-limit / 403 bot-block, a posture signal

leader.co.za

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

This reading of leader.co.za was taken 5d ago

leader.co.za is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting leader.co.za 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 leader.co.za Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Signed observation on record.
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 22:36 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 leader.co.za actually stands on - every host below is a signed observation
leader.co.za
A / AAAA
209.203.48.62
unattributedserves the site
NS
ns3.tld-ns.netns2.tld-ns.comns4.tld-ns.comns1.tld-ns.net
tld-ns.net + tld-ns.comanswers its DNS
MX
mx1.tld-mx.com
tld-mx.comreceives its email

DNS Records

A 1

  • 209.203.48.62

MX 1

  • 10mx1.tld-mx.com

TXT 1

  • v=spf1 +a +mx +ip4:196.3.176.134 include:_spf.tld-mx.com include:_spf.vox.co.za include:touchbasepro.email ~all

NS 4

  • ns3.tld-ns.net
  • ns2.tld-ns.com
  • ns4.tld-ns.com
  • ns1.tld-ns.net

SOA 1

  • ns1.tld-ns.net dns-admin.domains.co.za

MCP_RECORDS 1

  • v=spf1 +a +mx +ip4:196.3.176.134 include:_spf.tld-mx.com include:_spf.vox.co.za include:touchbasepro.email ~all

DMARC_RECORDS 1

  • v=DMARC1; p=reject; aspf=s;

BIMI_RECORDS 1

  • v=spf1 +a +mx +ip4:196.3.176.134 include:_spf.tld-mx.com include:_spf.vox.co.za include:touchbasepro.email ~all

MTA_STS_RECORDS 1

  • v=spf1 +a +mx +ip4:196.3.176.134 include:_spf.tld-mx.com include:_spf.vox.co.za include:touchbasepro.email ~all

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_d96531b79f1e6fcb
Output Hash
2060aeec29120ad7977c55760c311a7cfcf5f089fbcb25b4add9da348d3cb3c5
Signature
ed25519:1e32d62b43941cb41064bd841968408fbe5144aa647966ffa659e87aed47c1269d4f8b9e77a12506febb9f4b0fa2e97ae82328ea5feb5932727a4d9849deb600
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser