CONTINUOUS INTERNET TELEMETRY24H DRIFT31,420 material changesacross 29,745 domains · last 24hSHIFT18 domains moved DNS from brainydns.com to koaladns.coma coordinated move · 24hNOW560 curated domains not reachablelast probe, steadySITE ERRORS34,183 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,263 sites429 rate-limit / 403 bot-block, a posture signal

usign.io

Observed Aug 3, 2026, 03:28 UTC (21h ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.

Up right now
Email byGoogle Workspace
Secured byLet's Encrypt
Also usesGoogle Search Console
IPv6 · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-03 23:29 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 usign.io actually stands on - every host below is a signed observation
usign.io
A / AAAA
148.113.218.1552607:5300:203:5c03::1
2607serves the site
NS
ns-1236.awsdns-26.orgns-1573.awsdns-04.co.ukns-182.awsdns-22.comns-710.awsdns-24.net
awsdns-26.org + awsdns-04.co.uk + moreanswers its DNS
MX
aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comalt1.aspmx.l.google.com+1 more
Google Workspacereceives its email
TLS
usign.io
Let's Encryptissued its certificate

DNS Records

A 1

  • 148.113.218.155

AAAA 1

  • 2607:5300:203:5c03::1

MX 5

  • 1aspmx.l.google.com
  • 10alt3.aspmx.l.google.com
  • 10alt4.aspmx.l.google.com
  • 5alt1.aspmx.l.google.com
  • 5alt2.aspmx.l.google.com

TXT 1

  • google-site-verification=Wf0hHmcGiCQSe3ePoEQUM5pt354-YdlVrfts2DuyjIQ

NS 4

  • ns-1236.awsdns-26.org
  • ns-1573.awsdns-04.co.uk
  • ns-182.awsdns-22.com
  • ns-710.awsdns-24.net

SOA 1

  • ns-710.awsdns-24.net awsdns-hostmaster.amazon.com

CAA 4

  • iodef "mailto:tecnologia@jbtec.com.br"
  • issue "letsencrypt.org"
  • issuewild "digicert.com"
  • issuewild "letsencrypt.org"

MCP_RECORDS 1

  • google-site-verification=Wf0hHmcGiCQSe3ePoEQUM5pt354-YdlVrfts2DuyjIQ

DMARC_RECORDS 1

  • google-site-verification=Wf0hHmcGiCQSe3ePoEQUM5pt354-YdlVrfts2DuyjIQ

BIMI_RECORDS 1

  • google-site-verification=Wf0hHmcGiCQSe3ePoEQUM5pt354-YdlVrfts2DuyjIQ

MTA_STS_RECORDS 1

  • google-site-verification=Wf0hHmcGiCQSe3ePoEQUM5pt354-YdlVrfts2DuyjIQ

TLS Certificates (3)

Common NameIssuerExpires
usign.io C=US, O=Let's Encrypt, CN=YR1 Sun, 18 Oct 2026 05:17:49 +0000
YR1 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 (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_83ee415c45737ec1
Output Hash
7e9f6ecf197556a2651f26d9b824ab100a28c10b1b0491073e456818726e5737
Signature
ed25519:6d0e8b15c86df8c506441e0ce03c5958512fd515d2f808f16d9839285953080f9a9c432f850e9b5d2c816d07259a7b10398bd91f02c63a1bb4b34e07167abe0f
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser