bloomwise.nl
Observed Aug 12, 2026, 05:58 UTC (5d ago). Every field below was attested with an Ed25519 signature at scan time.
bloomwise.nl is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting bloomwise.nl 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 bloomwise.nl Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Google Workspace
Let's EncryptSteady. No change on record for bloomwise.nl 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 1
31.14.99.83
AAAA 1
2a01:7c8:bb02:521:5054:ff:fe25:6ddf
MX 5
1aspmx.l.google.com5alt1.aspmx.l.google.com5alt2.aspmx.l.google10alt3.aspmx.l.google.com10alt4.aspmx.l.google.com
TXT 1
v=spf1 a include:_spf.bloomwise.nl include:_spf.google.com include:_spf.transip.email ~all
NS 2
ns1.premium-dns.nlns2.premium-dns.eu
SOA 1
ns1.premium-dns.nl domain.okhost.nl
MCP_RECORDS 1
v=spf1 a ip4:94.237.109.103 include:_spf.bloomwise.nl include:_spf.google.com ~all
DMARC_RECORDS 1
v=DMARC1; p=quarantine; rua=mailto:dmarc@taalendigitaal.nl
BIMI_RECORDS 1
v=spf1 a ip4:94.237.109.103 include:_spf.bloomwise.nl include:_spf.google.com ~all
MTA_STS_RECORDS 1
v=spf1 a ip4:94.237.109.103 include:_spf.bloomwise.nl include:_spf.google.com ~all
TLS Certificates (3)
| Common Name | Issuer | Expires |
|---|---|---|
bloomwise.nl |
C=US, O=Let's Encrypt, CN=YR1 | Sun, 18 Oct 2026 18:23:08 +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)
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_accb476250f52545- Output Hash
b891c33f5d4a63c09a494ca1df5d48fb2097e0e7e47504d95104029261bc3c02- Signature
ed25519:78c90ea92a918f1a688db7ad081d12cd6d741abbd2a56e1d00a9b593b19f0db0f4fc5303555ab9d829f869ba875506303c8a1c467d13709da43dfc8ae2bb5a0b- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast