CONTINUOUS INTERNET TELEMETRY24H DRIFT27,060 material changesacross 26,158 domains · 24h to ~13h ago · -10,962 vs yesterdayROTATION58 domains moved DNS from kirklanddc.com to koaladns.com, 56 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW561 curated domains not reachable+30 vs yesterdaySITE ERRORS33,742 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,733 sites429 rate-limit / 403 bot-block, a posture signal

dynainbox.com

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

This reading of dynainbox.com was taken 5d ago

dynainbox.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting dynainbox.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 dynainbox.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Signed observation on record.
IPv6 · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 16:39 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 dynainbox.com actually stands on - every host below is a signed observation
dynainbox.com
A / AAAA
188.40.59.2082a01:4f8:172:35ec::2
2a01serves the site
NS
d.ns14.netc.ns14.netb.ns14.net
ns14.netanswers its DNS
MX
mail.dynainbox.com
dynainbox.comreceives its email

DNS Records

A 1

  • 188.40.59.208

AAAA 1

  • 2a01:4f8:172:35ec::2

MX 1

  • 5mail.dynainbox.com

TXT 2

  • type=1
  • v=spf1 exists:%{h}.h.%{ir}._spf.dynainbox.com ?all

NS 3

  • d.ns14.net
  • c.ns14.net
  • b.ns14.net

SOA 1

  • ns.dynainbox.com hostmaster.dynainbox.com

MCP_RECORDS 2

  • type=1
  • v=spf1 exists:%{h}.h.%{ir}._spf.dynainbox.com ?all

DMARC_RECORDS 1

  • v=DMARC1; p=none; pct=100; rua=mailto:dmarc-agg@dynainbox.com; ruf=mailto:dmarc-forensic@dynainbox.com; ri=3600; fo=0:1:d:s; aspf=s; adkim=s;

BIMI_RECORDS 2

  • type=1
  • v=spf1 exists:%{h}.h.%{ir}._spf.dynainbox.com ?all

MTA_STS_RECORDS 2

  • type=1
  • v=spf1 exists:%{h}.h.%{ir}._spf.dynainbox.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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_3d8502cf07ca82e7
Output Hash
0ff4d05748f5c6d08775dbf96a61fa161ccff9241f6fab09783ebe521c742267
Signature
ed25519:60e5c55bb7e25c9b0edd7e5649f6b9473d79882f5407cd23e6b5c4ca9c02bc8e2538520b304b43758c7e795e53a2dd09398b1b693fdb763a5035d1846d967407
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser