CONTINUOUS INTERNET TELEMETRY24H DRIFT34,178 material changesacross 31,769 domains · 24h to ~2h agoDNS DRIFT54 domains changed DNS providertop destination koaladns.com · +32 vs yesterdayNOW556 curated domains not reachablelast probe, steadySITE ERRORS33,680 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 157,156 sites429 rate-limit / 403 bot-block, a posture signal

domaineinternet.ca

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

This reading of domaineinternet.ca was taken 2d ago

domaineinternet.ca is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting domaineinternet.ca 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 domaineinternet.ca 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
Email byGoogle (SPF sender)
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 09:32 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 domaineinternet.ca actually stands on - every host below is a signed observation
domaineinternet.ca
A / AAAA
173.209.57.106
unattributedserves the site
NS
ns2.softlayer.comns1.softlayer.com
softlayer.comanswers its DNS
MX
mail.domaineinternet.ca
Google (SPF sender)receives its email

DNS Records

A 1

  • 173.209.57.106

MX 1

  • 0mail.domaineinternet.ca

TXT 1

  • v=spf1 a mx ip4:158.85.89.116 ip4:158.85.77.121 ip4:64.98.0.0/15 include:_spf.google.com ~all

NS 2

  • ns2.softlayer.com
  • ns1.softlayer.com

SOA 1

  • ns1.softlayer.com support.softlayer.com

MCP_RECORDS 1

  • v=spf1 a mx ip4:158.85.89.116 ip4:158.85.77.121 ip4:64.98.0.0/15 include:_spf.google.com ~all

DMARC_RECORDS 1

  • v=spf1 a mx ip4:158.85.89.116 ip4:158.85.77.121 ip4:64.98.0.0/15 include:_spf.google.com ~all

BIMI_RECORDS 1

  • v=spf1 a mx ip4:158.85.89.116 ip4:158.85.77.121 ip4:64.98.0.0/15 include:_spf.google.com ~all

MTA_STS_RECORDS 1

  • v=spf1 a mx ip4:158.85.89.116 ip4:158.85.77.121 ip4:64.98.0.0/15 include:_spf.google.com ~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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_1ed283fd55c3f4cf
Output Hash
7a8d27c0e2f43aea1e8be7f9166564d40a0aae50384b85e8910e2cbc0fa529d9
Signature
ed25519:c1a0cf3676473ea6eee54d4fe94d25d31a076655ffe5490b588d47c206d8c866393da2b563e53bc022419659ecf0641a3d937a6ca1cc9a5e43d64cbd6ce0e80e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser