CONTINUOUS INTERNET TELEMETRY24H DRIFT37,653 material changesacross 34,127 domains · 24h to ~35m agoDNS DRIFT55 domains changed DNS providertop destination koaladns.com · +33 vs yesterdayNOW560 curated domains not reachablelast probe, steadySITE ERRORS33,330 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,423 sites429 rate-limit / 403 bot-block, a posture signal

amiga.dev

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

This reading of amiga.dev was taken 2d ago

amiga.dev is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting amiga.dev 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 amiga.dev Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Email byGoogle Workspace
Secured byLet's Encrypt
Also usesGoogle Search Console
1 subdomain · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 13: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 amiga.dev actually stands on - every host below is a signed observation
amiga.dev
A / AAAA
89.233.108.254
unattributedserves the site
NS
ns1.amigadev.comns4.amigadev.comns2.amigadev.comns3.amigadev.com+1 more
amigadev.comanswers its DNS
MX
aspmx5.googlemail.comaspmx2.googlemail.comalt1.aspmx.l.google.comaspmx4.googlemail.com+3 more
Google Workspacereceives its email
TLS
www.amigadev.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 89.233.108.254

MX 7

  • 10aspmx5.googlemail.com
  • 10aspmx2.googlemail.com
  • 5alt1.aspmx.l.google.com
  • 10aspmx4.googlemail.com
  • 1aspmx.l.google.com
  • 5alt2.aspmx.l.google.com
  • 10aspmx3.googlemail.com

TXT 2

  • google-site-verification=fhCQsoDOItPJT1aibEZFdzqR416mKp1M2h8cI91-PXs
  • v=spf1 ip4:207.126.144.0/20 ip4:64.18.0.0/20 ip4:74.125.148.0/22 include:_spf.google.com ~all

NS 5

  • ns1.amigadev.com
  • ns4.amigadev.com
  • ns2.amigadev.com
  • ns3.amigadev.com
  • ns5.amigadev.com

SOA 1

  • ns1.amigadev.com marlon.amigadev.com

MCP_RECORDS 2

  • v=spf1 ip4:207.126.144.0/20 ip4:64.18.0.0/20 ip4:74.125.148.0/22 include:_spf.google.com ~all
  • google-site-verification=fhCQsoDOItPJT1aibEZFdzqR416mKp1M2h8cI91-PXs

DMARC_RECORDS 2

  • v=spf1 ip4:207.126.144.0/20 ip4:64.18.0.0/20 ip4:74.125.148.0/22 include:_spf.google.com ~all
  • google-site-verification=fhCQsoDOItPJT1aibEZFdzqR416mKp1M2h8cI91-PXs

BIMI_RECORDS 2

  • google-site-verification=fhCQsoDOItPJT1aibEZFdzqR416mKp1M2h8cI91-PXs
  • v=spf1 ip4:207.126.144.0/20 ip4:64.18.0.0/20 ip4:74.125.148.0/22 include:_spf.google.com ~all

MTA_STS_RECORDS 2

  • v=spf1 ip4:207.126.144.0/20 ip4:64.18.0.0/20 ip4:74.125.148.0/22 include:_spf.google.com ~all
  • google-site-verification=fhCQsoDOItPJT1aibEZFdzqR416mKp1M2h8cI91-PXs

TLS Certificates (3)

Common NameIssuerExpires
www.amigadev.com C=US, O=Let's Encrypt, CN=YR2 Wed, 02 Sep 2026 12:19:42 +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 (1)

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_20939e5b8e05df49
Output Hash
a473b91e8858c4933bdf06f18ffc7c8c83e891a3a8eb961d86f2120c1e266b76
Signature
ed25519:9fb15f86b84e2c21fdcd1fb571f93c8b62d174aa915c72d89462809871710c0ec4fa3586614f56823c4158bd093c01b569ffe10683397c5e1eff514b192fcc03
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser