CONTINUOUS INTERNET TELEMETRY24H DRIFT62,563 material changesacross 59,341 domains · 24h to ~2h ago · +27,946 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW536 curated domains not reachablelast probe, steadySITE ERRORS33,804 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 130,707 sites429 rate-limit / 403 bot-block, a posture signal

redhillsee.net

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

This reading of redhillsee.net was taken 3d ago

redhillsee.net is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting redhillsee.net 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 redhillsee.net Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byZeroSSL GmbH
IPv6 · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 03:55 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 redhillsee.net actually stands on - every host below is a signed observation
redhillsee.net
A / AAAA
34.41.139.1932600:1900:4001:96e:8000:1:e0a5:7bb6
2600serves the site
NS
ns2.hwrn.netns1.hwrn.net
hwrn.netanswers its DNS
MX
mx2.csof.netmx1.csof.net
csof.netreceives its email
TLS
*.redhillsee.net
ZeroSSL GmbHissued its certificate

DNS Records

A 1

  • 34.41.139.193

AAAA 1

  • 2600:1900:4001:96e:8000:1:e0a5:7bb6

MX 2

  • 10mx2.csof.net
  • 10mx1.csof.net

TXT 1

  • v=spf1 include:_incspfcheck.mailspike.net -all

NS 2

  • ns2.hwrn.net
  • ns1.hwrn.net

SOA 1

  • ns1.hwrn.net hostmaster.hwrn.net

MCP_RECORDS 1

  • v=spf1 include:_incspfcheck.mailspike.net -all

DMARC_RECORDS 1

  • v=spf1 include:_incspfcheck.mailspike.net -all

BIMI_RECORDS 1

  • v=spf1 include:_incspfcheck.mailspike.net -all

MTA_STS_RECORDS 1

  • v=spf1 include:_incspfcheck.mailspike.net -all

TLS Certificates (2)

Common NameIssuerExpires
*.redhillsee.net C=AT, O=ZeroSSL GmbH, CN=ZeroSSL RSA DV SSL CA 2 Sun, 13 Sep 2026 23:59:59 +0000
ZeroSSL RSA DV SSL CA 2 C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication Root R46 Sun, 23 Sep 2035 23:59:59 +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_1429a8c46e75588e
Output Hash
35a0801a9f8b494bdc08419136cc29819a30847a7d707d80ca4f872e42da6dab
Signature
ed25519:bdb4f486a85c9dc83c664862425173cc738cb622cee9b18a33d6063c707e193ba1cec55051f835651d7f4dcf26f6687bf809b11dc16836be07c5c5063ed1130a
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser