power-man.dk

📜 Historical scan 2026-08-12 09:54:35 · ← Latest scan

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

power-man.dk is a registered .dk domain whose nameservers (dns106.ovh.net, ns106.ovh.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 13 September 2013 (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 683ms

Nameserver	IP addresses	PTR	ASN / ISP
dns106.ovh.net	2001:41d0:d01::2 5.196.41.1	dns106.ovh.net dns106.ovh.net	AS16276 OVH SAS AS16276 OVH SAS
ns106.ovh.net	2001:41d0:b00:fa00::2 5.135.65.21	ns106.ovh.net ns106.ovh.net	AS16276 OVH SAS AS16276 OVH SAS

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

798ms

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 07:28:30

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2013-09-13
Expires	2027-09-30 (342d)

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

683ms

685ms

689ms

AAAA

671ms

TXT

2653ms

CAA

678ms

HTTPS

613ms

TLSA

459ms

SOA

218ms

MTA-STS

722ms

DNSSEC

798ms

SRV

682ms

Total

5179ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 22:42:35	3661ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-25 13:06:49	3465ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 00:11:04	6537ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 22:40:29	5694ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 22:29:09	9776ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 22:19:12	11456ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 21:47:56	7632ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 20:48:53	2265ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 13:05:28	11791ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 17:34:31	2437ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 04:10:06	9380ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 09:54:35 shown	5179ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 01:56:58	6505ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 18:04:46	8624ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 17:44:41	3854ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 16:44:05	9506ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 07:03:10	11893ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 06:19:39	9209ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 05:32:34	3927ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 05:01:50	6611ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 04:00:01	7078ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 01:34:19	2509ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 23:06:18	2344ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 21:07:35	3861ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 13:20:44	2099ms	2 NS 0 A 0 MX	❓ Unknown