nickipedersen.dk

📜 Historical scan 2026-07-23 05:32:39 · ← Latest scan

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

nickipedersen.dk is a registered .dk domain whose nameservers (raq2.signal.dk, raq3.signal.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 8 January 2003 (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 4077ms

Nameserver	IP addresses	PTR	ASN / ISP
raq2.signal.dk	192.0.78.24 192.0.78.25	— —	AS2635 Automattic, Inc AS2635 Automattic, Inc
raq3.signal.dk	192.0.78.24 192.0.78.25	— —	AS2635 Automattic, Inc AS2635 Automattic, Inc

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

4100ms

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-14 11:32:08

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2003-01-08
Expires	2027-01-31 (102d)

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

4077ms

2078ms

4076ms

AAAA

4076ms

TXT

28260ms

CAA

4079ms

HTTPS

2071ms

TLSA

76ms

SOA

46ms

MTA-STS

2080ms

DNSSEC

4100ms

SRV

16055ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-27 13:47:27	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 13:53:13	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 11:58:42	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 11:27:43	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 09:27:37	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 03:08:25	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 14:35:47	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 02:32:30	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 02:14:47	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 21:41:02	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 03:33:55	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 17:47:16	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 13:34:52	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 01:51:51	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 14:01:28	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 08:14:39	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 07:04:38	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 06:27:26	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 05:59:50	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 05:32:39 shown	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 03:52:30	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 09:21:43	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 07:39:40	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-16 16:53:52	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-14 01:48:06	65535ms	2 NS 0 A 0 MX	❓ Unknown