CONTINUOUS INTERNET TELEMETRY24H DRIFT50,775 material changesacross 47,754 domains · 24h to ~2h ago · -11,301 vs yesterdayROTATION50 domains moved DNS from kirklanddc.com to koaladns.com, 49 moved backa rotation loop, not a migration · 24hNOW532 curated domains not reachablelast probe, steadySITE ERRORS33,880 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 120,115 sites429 rate-limit / 403 bot-block, a posture signal

ebcc.info

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

This reading of ebcc.info was taken 4d ago

ebcc.info is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting ebcc.info 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 ebcc.info Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
2 subdomains · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 03:03 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 ebcc.info actually stands on - every host below is a signed observation
ebcc.info
A / AAAA
185.175.84.97
unattributedserves the site
NS
ns.fortion.euns.fortion.netns.fortion.cz
fortion.eu + fortion.net + moreanswers its DNS
MX
mx1.fortion.netmx2.fortion.netmx0.fortion.net
fortion.netreceives its email
TLS
ebcc.info
Let's Encryptissued its certificate

DNS Records

A 1

  • 185.175.84.97

MX 3

  • 10mx1.fortion.net
  • 20mx2.fortion.net
  • 5mx0.fortion.net

TXT 1

  • v=spf1 a mx include:spf.smartemailing.cz ~all

NS 3

  • ns.fortion.eu
  • ns.fortion.net
  • ns.fortion.cz

SOA 1

  • ns.fortion.cz info.fortion.cz

MCP_RECORDS 1

  • v=spf1 a mx include:spf.smartemailing.cz ~all

DMARC_RECORDS 1

  • v=DMARC1; p=none;

BIMI_RECORDS 1

  • v=spf1 a mx include:spf.smartemailing.cz ~all

MTA_STS_RECORDS 1

  • v=spf1 a mx include:spf.smartemailing.cz ~all

TLS Certificates (3)

Common NameIssuerExpires
ebcc.info C=US, O=Let's Encrypt, CN=YR1 Wed, 21 Oct 2026 20:56:54 +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 (2)

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_d2be70cc90a2502a
Output Hash
d16c60eaac6ec034aeb34be10125f0e080f8adbd9ae06fe3f6debac1ddb0231d
Signature
ed25519:5e059c3eb30a89f1fe4531eac5cf425388b1ed3fc690e552d004e15114621ea40a4db423c87117f0bf38dcb234b1b1f763bfd5e5075ed49f7fd5da64e3a4f00d
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser