8270hhs.dk

📜 Historical scan 2026-07-31 17:05:42 · ← Latest scan

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

8270hhs.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 5 November 2010 (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 166ms

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#

190ms

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-20 05:30:01

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2010-11-05
Expires	2026-11-30 (37d)

🔗 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#

166ms

160ms

119ms

AAAA

126ms

TXT

611ms

CAA

165ms

HTTPS

125ms

TLSA

115ms

SOA

24ms

MTA-STS

123ms

DNSSEC

190ms

SRV

168ms

Total

1380ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 01:49:46	1243ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 02:37:28	3119ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 01:03:49	27392ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 00:56:06	1490ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 00:49:31	1185ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 00:06:28	1473ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 23:25:11	998ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 16:55:07	2886ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 04:54:29	51309ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 23:16:43	2796ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 19:39:41	1186ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 17:34:56	3037ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 09:11:58	10144ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 18:12:06	10087ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 13:01:54	1399ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 00:49:34	31079ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 17:05:42 shown	1380ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 00:27:15	1162ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 23:58:55	9044ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 23:51:16	10057ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 23:34:34	1353ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 22:46:52	10038ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 20:46:59	867ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 15:37:38	962ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 14:55:29	2251ms	2 NS 0 A 0 MX	❓ Unknown