nb-graveservice.dk

📜 Historical scan 2026-07-04 23:59:56 · ← Latest scan

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

nb-graveservice.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 6 October 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 247ms

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#

333ms

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-22 18:18:50

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2020-10-06
Expires	2026-10-31 (6d)

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

247ms

264ms

313ms

AAAA

301ms

TXT

1036ms

CAA

262ms

HTTPS

210ms

TLSA

192ms

SOA

305ms

MTA-STS

223ms

DNSSEC

333ms

SRV

305ms

Total

1650ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 02:01:53	1186ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-06 00:19:21	2786ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-04 08:33:44	6726ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 19:29:37	1417ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 17:48:06	1705ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 17:38:20	27174ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 17:34:08	5555ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 12:09:48	2420ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 12:05:56	1463ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 00:47:12	10237ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 19:55:17	2991ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 16:56:26	4132ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 16:29:31	2845ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 08:18:18	2552ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 00:18:27	16778ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 21:43:42	27138ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 03:36:55	2385ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 15:18:36	873ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 14:49:41	885ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 14:30:25	33211ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 14:03:58	807ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 11:52:28	9062ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 07:40:19	968ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 17:23:39	1141ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 16:16:52	24938ms	2 NS 0 A 0 MX	❓ Unknown