bf3blog.com
Observed Aug 16, 2026, 17:23 UTC (11h ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.
Steady. No change on record for bf3blog.com in the last day; this reading matches the one before it. The steady record is signed like every other reading. Watch it to catch the next move the moment it lands.
DNS Records
A 2
54.84.240.23544.208.83.180
AAAA 2
2600:1f18:4ae:c608:1ae1:9fc3:6ee2:84dd2600:1f18:4ae:c607:5974:bfa8:d54b:7fe5
TXT 1
v=spf1 -all
NS 2
ns1.namebrightdns.comns2.namebrightdns.com
SOA 1
ns1.namebrightdns.com dns.namebright.com
TLS Certificates (3)
| Common Name | Issuer | Expires |
|---|---|---|
bf3blog.com |
C=US, O=Let's Encrypt, CN=YE2 | Fri, 13 Nov 2026 16:42:33 +0000 |
YE2 |
C=US, O=ISRG, CN=Root YE | Sat, 02 Sep 2028 23:59:59 +0000 |
Root YE |
C=US, O=Internet Security Research Group, CN=ISRG Root X2 | Thu, 02 Sep 2032 23:59:59 +0000 |
Subdomains (0)
None observed.
DomainDrift asked this domain for one hostname that nobody ever registered, and it answered. A domain that answers invented hostnames is running wildcard DNS. It is common and usually deliberate. A SaaS platform gives every customer a subdomain this way. How the check works
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_bcf0dbc6e029f65e- Output Hash
cf6398b15439d479463b7c3903ee152ae9b9646f69d274a79c4f670530ab9039- Signature
ed25519:97a6afa91fe6de367904d23b71f9882a6f43aa2cc8e383ae468aec093658b4cd20cd82ff220bd1aebd8731e81c7ba6a2d306dfd722280cd978cc6252ac464a0b- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast