CONTINUOUS INTERNET TELEMETRY24H DRIFT41,685 material changesacross 38,305 domains · 24h to ~85m ago · +7,068 vs yesterdaySHIFT42 domains moved DNS from koaladns.com to magpiedns.coma coordinated move · 24hNOW540 curated domains not reachablelast probe, steadySITE ERRORS33,827 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 150,322 sites429 rate-limit / 403 bot-block, a posture signal

urbantimes.co

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

This reading of urbantimes.co was taken 2d ago

urbantimes.co is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting urbantimes.co 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 urbantimes.co Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Guarded by a firewall
Runs onCloudflare
Secured byDigiCert
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 11: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 urbantimes.co actually stands on - every host below is a signed observation
urbantimes.co
A / AAAA
64.190.63.222
Cloudflareserves the site
NS
ns2.sedoparking.comns1.sedoparking.com
sedoparking.comanswers its DNS
MX
localhost
localhostreceives its email
TLS
urbantimes.co
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
urbantimes.co C=US, O=DigiCert Inc, 2.5.4.11=www.digicert.com, CN=Encryption Everywhere DV TLS CA - G2 Tue, 25 Aug 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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_f7208c5d7aab5475
Output Hash
916af3a8d52480cff758c0ead30823e09b9521b82736518a3cad254a0542145b
Signature
ed25519:c5ab4f04b9c087b6f7fb2646d46e4b1e3dfbc7d39d7fa685314600b5240d85c6f6e1c6898095d4c7b1e1f8eb0f2172cbc911265c2d6e956bd49179c8b08f230a
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser