bitmark.com
Observed Aug 2, 2026, 21:53 UTC (11d ago). Every field below was attested with an Ed25519 signature at scan time.
bitmark.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting bitmark.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 bitmark.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Fastly
Google Workspace
Let's Encrypt
Google Search ConsoleDomainDrift 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.
DNS Records
A 4
185.199.110.153185.199.108.153185.199.109.153185.199.111.153
AAAA 4
2606:50c0:8002::1532606:50c0:8001::1532606:50c0:8000::1532606:50c0:8003::153
TXT 3
bitmark-account-verification=4affe57a87bc616ba110e8e6b631466c621c9515715802d76e05201a730e0e9a583c516fc9aee4bfc43a6e0420995b87b7adb4a736da8d87a3f8a4789d57150bcec44bd8-b2fa-4479-8201-f170b6e9b269=14b61529a07285aa2790024ec5fca36a2a326d5ca81469022c30f2044f3a5065v=spf1 -all
NS 4
ns-1490.awsdns-58.orgns-1833.awsdns-37.co.ukns-484.awsdns-60.comns-920.awsdns-51.net
SOA 1
ns-920.awsdns-51.net awsdns-hostmaster.amazon.com
CAA 3
issue "amazonaws.com"issue "letsencrypt.org"issuewild "amazonaws.com"
MCP_RECORDS 1
bitmark-account-verification=426f702165837812a3eca05dbebbee3a82f01bfc4d1bc08f74b6d4784f5aaf1a6b5c5f53ccd38902918eb7f6946ee20b44babcc4068c4075449f496b2af3040c
DMARC_RECORDS 1
v=DMARC1; p=reject; sp=reject; pct=100
BIMI_RECORDS 1
bitmark-account-verification=426f702165837812a3eca05dbebbee3a82f01bfc4d1bc08f74b6d4784f5aaf1a6b5c5f53ccd38902918eb7f6946ee20b44babcc4068c4075449f496b2af3040c
MTA_STS_RECORDS 1
bitmark-account-verification=426f702165837812a3eca05dbebbee3a82f01bfc4d1bc08f74b6d4784f5aaf1a6b5c5f53ccd38902918eb7f6946ee20b44babcc4068c4075449f496b2af3040c
TLS Certificates (3)
| Common Name | Issuer | Expires |
|---|---|---|
bitmark.com |
C=US, O=Let's Encrypt, CN=YR1 | Sun, 18 Oct 2026 14:11:21 +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)
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 receiptEd25519 Receipt
- Receipt ID
rcpt_7083b0384c6ba432- Output Hash
7649478ac524616157406999fb0647c951784e2913a0f4a7d81fd35ed81c8b12- Signature
ed25519:4d2044d8836d4b387e64db0626bd42bd560298ed98bad0ec69496818fb2e729e89c52309a93a24e198063da9474cd0785f1de116c646decd2183b8da2e411f01- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast