bhstof.dk

📜 Historical scan 2026-07-30 05:57:38 · ← Latest scan

🧟 Lame delegation ⬇ Zone File 📜 Timeline & History ⚡ Scan Now

bhstof.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 7 May 2020 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Below are all of its DNS records from this scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.

🖥️ Nameservers#

2 records 4030ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.one.com	195.206.121.10 2001:67c:28cc::10	ns01.one.com ns01.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns02.one.com	185.10.11.10 2001:67c:3c0::10	ns02.one.com ns02.one.com	AS51468 One.com A/S AS51468 One.com A/S

🌍 A Records#

🌍

No A records found

📧 MX Records#

📧

No MX records found

🔷 AAAA Records (IPv6)#

✗ No AAAA records — IPv6 not configured

🔐 HTTPS Records#

✗ No HTTPS RR — no SVCB/HTTPS service binding

📝 TXT Records#

📝

No TXT records found

✉️ SPF#

✗ No SPF record — mail spoofing not restricted

📨 DMARC#

✗ No DMARC record — mail spoofing not restricted

📬 MTA-STS#

✗ No MTA-STS policy — SMTP TLS not enforced

📈 TLSRPT#

✗ No TLSRPT record — no SMTP TLS failure reporting

📜 CAA Records#

✗ No CAA records — any CA may issue certificates

🔗 TLSA / DANE#

✗ No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

🔐 DNSSEC#

9159ms

Check	Result
Validation Status	❓ Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates)	✗ Not set
DS Record	✗ Not found
DNSKEY Record	✗ Not found
Flags	resolution failed: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-12 16:49:11

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2020-05-07
Expires	2027-05-31 (215d)

🔗 Same registrant#

0 domains

Other .dk domains whose WHOIS registrant has the same name and postal address. Matched on a keyed hash: the registrant's details are not stored or shown. Covers only domains whose WHOIS we have fetched (refreshed about monthly).

No other domain with this registrant in our WHOIS data yet

📋 WHOIS#

⏱️ Lookup Timing#

4030ms

4028ms

AAAA

4030ms

TXT

4497ms

CAA

4028ms

HTTPS

4027ms

TLSA

115ms

SOA

4029ms

MTA-STS

4035ms

DNSSEC

9159ms

SRV

4031ms

Total

14217ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-27 02:26:25	1773ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-09-28 08:48:52	2775ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-31 19:48:44	57384ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 12:43:14	1624ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-23 16:57:27	16686ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-22 08:49:36	1800ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-21 08:45:41	8921ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-20 05:26:48	4085ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-19 03:16:46	4541ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-17 23:03:51	4475ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-16 20:52:49	3756ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-15 05:51:04	4525ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-13 21:07:40	15283ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 12:19:35	780ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-11 09:46:11	2657ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-10 04:47:01	3265ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-08 10:54:47	781ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-06 16:39:34	1560ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-04 17:03:43	24935ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-01 04:03:33	2221ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-30 05:57:38 shown	14217ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 18:32:53	10093ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-26 18:17:38	862ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-25 17:59:03	10173ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-24 17:43:29	740ms	2 NS 0 A 0 MX	⚠️ Bogus