CONTINUOUS INTERNET TELEMETRY24H DRIFT68,088 material changesacross 64,935 domains · 24h to ~3h ago · +33,471 vs yesterdayROTATION56 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW538 curated domains not reachablelast probe, steadySITE ERRORS33,857 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 123,111 sites429 rate-limit / 403 bot-block, a posture signal

yorkshirehistory.com

Observed Jul 27, 2026, 19:46 UTC (9d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of yorkshirehistory.com was taken 9d ago

yorkshirehistory.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting yorkshirehistory.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 yorkshirehistory.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Not responding
Signed observation on record.
IPv6 · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 10:15 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 yorkshirehistory.com actually stands on - every host below is a signed observation
yorkshirehistory.com
A / AAAA
45.33.83.10096.126.111.16566.175.209.17945.79.167.180+4 more
2600serves the site
NS
damao.ns.giantpanda.comyangguang.ns.giantpanda.com
giantpanda.comanswers its DNS
MX
mail.mailerhost.net
mailerhost.netreceives its email

DNS Records

A 4

  • 45.33.83.100
  • 96.126.111.165
  • 66.175.209.179
  • 45.79.167.180

AAAA 4

  • 2600:3c03::f03c:95ff:fe91:5d52
  • 2600:3c03::f03c:95ff:feed:4d4f
  • 2600:3c03::f03c:95ff:fe00:29ca
  • 2600:3c03::f03c:95ff:feed:cf2a

MX 1

  • 1mail.mailerhost.net

TXT 5

  • v=spf1 ip6:fd43:c0d1:c090::/48 -all
  • v=spf1 ip6:fd43:c0d1:c090::/48 -all
  • v=spf1 ip6:fd43:c0d1:c090::/48 -all
  • v=spf1 ip6:fd43:c0d1:c090::/48 -all
  • v=spf1 ip6:fd43:c0d1:c090::/48 -all

NS 2

  • damao.ns.giantpanda.com
  • yangguang.ns.giantpanda.com

SOA 1

  • damao.ns.giantpanda.com admin.giantpanda.com

TLS Certificates (0)

None.

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