langleywa.org

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

This reading of langleywa.org was taken 3d ago

langleywa.org is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting langleywa.org 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 langleywa.org Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Guarded by a firewall
Secured byLet's Encrypt
1 subdomain · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-13 21:07 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 langleywa.org actually stands on - every host below is a signed observation
langleywa.org
A / AAAA
35.71.179.239
unattributedserves the site
NS
ns.whidbey.comns.whidbey.net
whidbey.com + whidbey.netanswers its DNS
MX
mx.whidbey.net
whidbey.netreceives its email
TLS
ssl3.revizesites.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 35.71.179.239

MX 1

  • 100mx.whidbey.net

TXT 1

  • v=spf1 ip4:209.166.64.0/19 ~all

NS 2

  • ns.whidbey.com
  • ns.whidbey.net

SOA 1

  • ns.whidbey.com hostmaster.whidbey.com

MCP_RECORDS 1

  • v=spf1 ip4:209.166.64.0/19 ~all

DMARC_RECORDS 1

  • v=DMARC1; p=none; rua=mailto:mailauth-reports@whidbey.com

BIMI_RECORDS 1

  • v=spf1 ip4:209.166.64.0/19 ~all

MTA_STS_RECORDS 1

  • v=spf1 ip4:209.166.64.0/19 ~all

TLS Certificates (3)

Common NameIssuerExpires
ssl3.revizesites.com C=US, O=Let's Encrypt, CN=YR1 Sun, 08 Nov 2026 13:45:00 +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 (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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_516db1b84030fcc1
Output Hash
6fb577323057862c35fea2553c2db1ae9b1b82d8873d76044320f241ec058de5
Signature
ed25519:6655ef9d2b2a64ff54d8d2dc434f87f19384c06b5a68e353e262d113fb72dceaae5af7079533d76c06656acdd8ab0f2e5c935c4bb43730ddd6232e4861327101
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT44,221 material changesacross 42,267 domains · 24h to ~80m ago · +139 vs yesterdayROTATION58 domains moved DNS from koaladns.com to magpiedns.com, 52 moved backa rotation loop, not a migration · 24hNOW492 curated domains not reachablelast probe, steadySITE ERRORS36,557 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 115,955 sites429 rate-limit / 403 bot-block, a posture signal