bnc.nl
Observed Aug 3, 2026, 09:29 UTC (10d ago). Every field below was attested with an Ed25519 signature at scan time.
bnc.nl is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting bnc.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 bnc.nl Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Microsoft 365
Let's Encrypt
Apple
CiscoDomainDrift 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 1
91.233.22.79
MX 1
0bnc-nl.y-v1.mx.microsoft
TXT 7
MS=ms74662578apple-domain-verification=fvh7iFIwvyP5SMWrMS=576CC0AC415B2F5629FEF6C8D3D97DF7BB8261D8duo_sso_verification=77WtSNRcHrfXPAPRWk8S6GT4IQPR91KntXKzjw0D7OYRVYIRx6QiFNH9QJrzg1LCciscocidomainverification=200c208d9dde3e3721a75e1e478d9d7045776b7f9eef87773921e9de7392ddb2v=spf1 include:spf.protection.outlook.com include:spf-a.bnc.nl include:_spf.mlsend.com include:amazonses.com ~allduo_sso_verification=77WtSNRcHrfXPAPRWk8S6GT4IQPR91KntXKzjw0D7OYRVYIRx6QiFNH9QJrzg1LCPRWk8S6GT4IQPR91KntXKzjw0D7OYRVYIRx6QiFNH9QJrzg1LC
NS 3
ns0.transip.netns1.transip.nlns2.transip.eu
SOA 1
ns0.transip.net hostmaster.transip.nl
MCP_RECORDS 1
duo_sso_verification=77WtSNRcHrfXPAPRWk8S6GT4IQPR91KntXKzjw0D7OYRVYIRx6QiFNH9QJrzg1LC
DMARC_RECORDS 1
v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc_rua@bnc.nl; ruf=mailto:dmarc_ruf@bnc.nl; fo=1
BIMI_RECORDS 1
duo_sso_verification=77WtSNRcHrfXPAPRWk8S6GT4IQPR91KntXKzjw0D7OYRVYIRx6QiFNH9QJrzg1LC
MTA_STS_RECORDS 1
duo_sso_verification=77WtSNRcHrfXPAPRWk8S6GT4IQPR91KntXKzjw0D7OYRVYIRx6QiFNH9QJrzg1LC
TLS Certificates (4)
| Common Name | Issuer | Expires |
|---|---|---|
bnc.nl |
C=US, O=Let's Encrypt, CN=YE1 | Thu, 22 Oct 2026 05:54:26 +0000 |
YE1 |
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 |
ISRG Root X2 |
C=US, O=Internet Security Research Group, CN=ISRG Root X1 | Thu, 02 Sep 2032 23:59:59 +0000 |
Subdomains (2)
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_1bb59c870cb5bd8f- Output Hash
66787ef36167526fedb43f03e41868c69059fb6fb2c219e7194117b44fb5f9e2- Signature
ed25519:46f6ca65e6ca38a3ac675340532ef2f3a2ffb88ce1a01f4719790e41dfd7ff140845e0e8fed40f033d11fe5d4f32d7834f350af69eb39f83df44f388a3571506- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast