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

url.to

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

This reading of url.to was taken 1d ago

url.to is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting url.to 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 url.to Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Up right now
Secured byDigiCert
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 22:51 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 url.to actually stands on - every host below is a signed observation
url.to
A / AAAA
64.190.63.222
unattributedserves the site
NS
ns2.sedoparking.comns1.sedoparking.com
sedoparking.comanswers its DNS
MX
localhost
localhostreceives its email
TLS
url.to
DigiCert Incissued its certificate

DNS Records

A 1

  • 64.190.63.222

MX 1

  • 0localhost

TXT 1

  • v=spf1 -all

NS 2

  • ns2.sedoparking.com
  • ns1.sedoparking.com

SOA 1

  • ns1.sedoparking.com hostmaster.sedo.de

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=spf1 -all

BIMI_RECORDS 1

  • v=spf1 -all

MTA_STS_RECORDS 1

  • v=spf1 -all

TLS Certificates (2)

Common NameIssuerExpires
url.to C=US, O=DigiCert Inc, 2.5.4.11=www.digicert.com, CN=Encryption Everywhere DV TLS CA - G2 Fri, 23 Oct 2026 23:59:59 +0000
Encryption Everywhere DV TLS CA - G2 C=US, O=DigiCert Inc, 2.5.4.11=www.digicert.com, CN=DigiCert Global Root G2 Sat, 27 Nov 2027 12:46:40 +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_287b2aee8cebc14b
Output Hash
c15acf4502cf17114edbc88bf3817d9d429d13e541fa1ced7c2cf2b0a1119cdb
Signature
ed25519:60917ad11e03feaf49047c66782ef13eb9e2d5cd5affdca6473979e0874ca76880e7f620ae902e794f3a991689cd39c6193032ce04a8bdcadd2a0b66f318cd02
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser