pimpyourname.dk

📜 Historical scan 2026-08-10 18:36:40 · ← Latest scan

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

pimpyourname.dk is a registered .dk domain whose nameservers (ns1.ns-serve.net, ns2.ns-serve.net) do not answer for it, so it is currently a lame delegation and does not resolve. It 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 783ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.ns-serve.net	195.191.92.140 2001:67c:2394:2::1001	ns1.ns-serve.net ns1.ns-serve.net	AS57115 Vautron Rechenzentrum AG AS25504 Vautron Rechenzentrum AG
ns2.ns-serve.net	195.191.93.140 2001:67c:2394:4::1001	ns2.ns-serve.net ns2.ns-serve.net	AS57115 Vautron Rechenzentrum AG AS25504 Vautron Rechenzentrum AG

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

988ms

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#

✗ No registration data yet — queued for a WHOIS lookup

📋 WHOIS#

⏱️ Lookup Timing#

783ms

809ms

816ms

AAAA

812ms

TXT

3172ms

CAA

820ms

HTTPS

800ms

TLSA

560ms

SOA

220ms

MTA-STS

948ms

DNSSEC

988ms

SRV

844ms

Total

6183ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-20 21:15:54	10894ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-08 04:04:43	3987ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-27 00:44:28	11841ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 21:56:21	3904ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 12:14:00	5525ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 10:59:48	1954ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 10:29:48	5170ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 09:12:32	4644ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 04:17:54	4350ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 02:15:46	6375ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 07:53:57	11890ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 19:17:27	2008ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 02:13:33	5524ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 18:36:40 shown	6183ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 14:16:59	6868ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 10:38:40	4179ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 10:40:15	5141ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 05:22:47	14260ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 04:42:44	2022ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 04:18:49	3527ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 03:52:29	10172ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 03:25:02	6798ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 02:17:23	2052ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 01:22:49	4107ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 01:20:41	4832ms	2 NS 0 A 0 MX	❓ Unknown