biblemapper.com

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

This reading of biblemapper.com was taken 2d ago

biblemapper.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting biblemapper.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 biblemapper.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onMicrosoft Corporation
Secured byLet's Encrypt
Registered withTucows Domains Inc.
Also usesGoogle Search Console
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 14:42 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 biblemapper.com actually stands on - every host below is a signed observation
biblemapper.com
A / AAAA
172.208.70.127
Microsoft Corporationserves the site
NS
ns2.turbify.comns1.turbify.com
turbify.comanswers its DNS
MX
mx-biz.mail.am0.yahoodns.netmx-biz.mail.am0.yahoodns.net
yahoodns.netreceives its email
TLS
www.biblemapper.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 172.208.70.127

MX 2

  • 20mx-biz.mail.am0.yahoodns.net
  • 30mx-biz.mail.am0.yahoodns.net

TXT 1

  • google-site-verification=ANihpO2D5eth6d7qYmmcPABS5d5gL9bz1ubLtfumPrQ

NS 2

  • ns2.turbify.com
  • ns1.turbify.com

SOA 1

  • ns1.turbify.com hostmaster.biblemapper.com

MCP_RECORDS 1

  • v=spf1 a mx ip4:172.208.70.127 include:relay.mailchannels.net -all

DMARC_RECORDS 1

  • v=spf1 a mx ip4:172.208.70.127 include:relay.mailchannels.net -all

BIMI_RECORDS 1

  • v=spf1 a mx ip4:172.208.70.127 include:relay.mailchannels.net -all

MTA_STS_RECORDS 1

  • v=spf1 a mx ip4:172.208.70.127 include:relay.mailchannels.net -all

TLS Certificates (3)

Common NameIssuerExpires
www.biblemapper.com C=US, O=Let's Encrypt, CN=YR1 Sun, 01 Nov 2026 02:43:55 +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_61f65a00800ef8de
Output Hash
1b1a682a5103f842744103724db4868098902b187332b6ba5936c1d8e4233747
Signature
ed25519:2a8cdb4ed3ba64c62a2e77c6f1b3a72bdf4e61ba76ed6b1882033a8127b176575f037eaf74330d0879c217e4ee2b8477817dbf59fa0788291e9fb4bd20db1e0f
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT47,489 material changesacross 45,291 domains · 24h to ~35m ago · +1,619 vs yesterdayROTATION60 domains moved DNS from magpiedns.com to koaladns.com, 57 moved backa rotation loop, not a migration · 24hNOW492 curated domains not reachablelast probe, steadySITE ERRORS36,278 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 115,598 sites429 rate-limit / 403 bot-block, a posture signal