CONTINUOUS INTERNET TELEMETRY24H DRIFT34,504 material changesacross 32,163 domains · 24h to ~2h agoDNS DRIFT55 domains changed DNS providertop destination koaladns.com · +33 vs yesterdayNOW559 curated domains not reachablelast probe, steadySITE ERRORS33,449 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,636 sites429 rate-limit / 403 bot-block, a posture signal

zortssports.com

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

This reading of zortssports.com was taken 2d ago

zortssports.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zortssports.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 zortssports.com 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 usesHubSpot
1 subdomain · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-03 22:26 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 zortssports.com actually stands on - every host below is a signed observation
zortssports.com
A / AAAA
68.183.248.189
unattributedserves the site
NS
ns1.digitalocean.comns2.digitalocean.comns3.digitalocean.com
digitalocean.comanswers its DNS
MX
alt3.aspmx.l.google.comalt2.aspmx.l.google.comaspmx.l.google.comalt1.aspmx.l.google.com+1 more
Google Workspacereceives its email
TLS
www.zortssports.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 68.183.248.189

MX 5

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

TXT 1

  • v=spf1 include:amazonses.com include:242205169.spf02.hubspotemail.net include:_spf.google.com ~all

NS 3

  • ns1.digitalocean.com
  • ns2.digitalocean.com
  • ns3.digitalocean.com

SOA 1

  • ns1.digitalocean.com hostmaster.zortssports.com

MCP_RECORDS 1

  • v=spf1 include:amazonses.com include:242205169.spf02.hubspotemail.net include:_spf.google.com ~all

DMARC_RECORDS 1

  • v=DMARC1; p=none; rua=mailto:engineering@zortssports.com

BIMI_RECORDS 1

  • v=spf1 include:amazonses.com include:242205169.spf02.hubspotemail.net include:_spf.google.com ~all

MTA_STS_RECORDS 1

  • v=spf1 include:amazonses.com include:242205169.spf02.hubspotemail.net include:_spf.google.com ~all

TLS Certificates (4)

Common NameIssuerExpires
www.zortssports.com C=US, O=Let's Encrypt, CN=YE2 Wed, 02 Sep 2026 06:01:35 +0000
YE2 C=US, O=ISRG, CN=Root YE Sat, 02 Sep 2028 23:59:59 +0000
Root YE C=US, O=Internet Security Research Group, CN=ISRG Root X2 Thu, 02 Sep 2032 23:59:59 +0000
ISRG Root X2 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_096cb9e147382f34
Output Hash
6b4c1ee5b14bb5b6b6728667e2ca3846826b4799ffdfa27ed545ad34f8a6943e
Signature
ed25519:c5c28e9c3d31e1fcf68d6d3b47552667c5d0f1db664f35e0563c3e10b3aae3c5d71221b03eb11be268662a33e6f10f49a9384735ddaf5ba9f6ea37b126360b05
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser