CONTINUOUS INTERNET TELEMETRY24H DRIFT48,392 material changesacross 43,424 domains · 24h to ~60m ago · +13,986 vs yesterdayROTATION55 domains moved DNS from koaladns.com to magpiedns.com, 54 moved backa rotation loop, not a migration · 24hNOW611 curated domains not reachablelast probe, steadySITE ERRORS34,178 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,838 sites429 rate-limit / 403 bot-block, a posture signal

repo.com

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

This reading of repo.com was taken 7d ago

repo.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting repo.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 repo.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onCloudflare
Secured byGoogle Trust Services
Also usesFacebook/MetaGoogle 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-09 10:13 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 repo.com actually stands on - every host below is a signed observation
repo.com
A / AAAA
172.67.176.245104.21.43.812606:4700:3031::ac43:b0f52606:4700:3031::6815:2b51
Cloudflareserves the site
NS
aiden.ns.cloudflare.comdell.ns.cloudflare.com
cloudflare.comanswers its DNS
MX
mail.ezprovider.com
ezprovider.comreceives its email
TLS
repo.com
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 172.67.176.245
  • 104.21.43.81

AAAA 2

  • 2606:4700:3031::ac43:b0f5
  • 2606:4700:3031::6815:2b51

MX 1

  • 10mail.ezprovider.com

TXT 3

  • facebook-domain-verification=jq6bg00ia8infz869h9r1qnzngo7h6
  • google-site-verification=2jjdjuLwYQoH39SHB_mwmdBeLwFPPxhemCnl0xqCvY8
  • v=spf1 a:repo.com a:mta1.repo.com include:ezprovider.com mx ~all

NS 2

  • aiden.ns.cloudflare.com
  • dell.ns.cloudflare.com

SOA 1

  • aiden.ns.cloudflare.com dns.cloudflare.com

MCP_RECORDS 3

  • facebook-domain-verification=jq6bg00ia8infz869h9r1qnzngo7h6
  • google-site-verification=2jjdjuLwYQoH39SHB_mwmdBeLwFPPxhemCnl0xqCvY8
  • v=spf1 a:repo.com a:mta1.repo.com include:ezprovider.com mx ~all

DMARC_RECORDS 1

  • v=DMARC1; p=quarantine; rua=mailto:7b5579a3@in.mailhardener.com,mailto:dmarc@ezprovider.com

BIMI_RECORDS 3

  • facebook-domain-verification=jq6bg00ia8infz869h9r1qnzngo7h6
  • google-site-verification=2jjdjuLwYQoH39SHB_mwmdBeLwFPPxhemCnl0xqCvY8
  • v=spf1 a:repo.com a:mta1.repo.com include:ezprovider.com mx ~all

MTA_STS_RECORDS 3

  • facebook-domain-verification=jq6bg00ia8infz869h9r1qnzngo7h6
  • google-site-verification=2jjdjuLwYQoH39SHB_mwmdBeLwFPPxhemCnl0xqCvY8
  • v=spf1 a:repo.com a:mta1.repo.com include:ezprovider.com mx ~all

TLS Certificates (3)

Common NameIssuerExpires
repo.com C=US, O=Google Trust Services, CN=WE1 Sun, 06 Sep 2026 23:10:57 +0000
WE1 C=US, O=Google Trust Services LLC, CN=GTS Root R4 Tue, 20 Feb 2029 14:00:00 +0000
GTS Root R4 C=BE, O=GlobalSign nv-sa, 2.5.4.11=Root CA, CN=GlobalSign Root CA Fri, 28 Jan 2028 00:00:42 +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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_68e6ad6c057f61cf
Output Hash
b2aae925087463a7a72e5271da1fbba90dce5889278ec9dd4abc51e689fa76d6
Signature
ed25519:47238a95881c5e49e6017248777b12adf11374c5bde49583a9f1970bc3965c6fb5a1f998a4cb860c01fcb717bff1197dac0f6acf3bdf4435245aab0898245609
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser