wattpower.dk

📜 Historical scan 2026-09-30 03:37:10 · ← Latest scan

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

wattpower.dk is a registered .dk domain whose nameservers (ns1.e-tiger.net, ns2.ns0.hu) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 13 August 2025 (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 702ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.e-tiger.net	193.23.139.1 2a00:1608:1608:1608::11	ns1.e-tiger.net ns1.e-tiger.net	AS51275 Viacom Informatics Ltd. AS51275 Viacom Informatics Ltd.
ns2.ns0.hu	2a01:6ee0:30:32::2 46.29.136.175	server1.zoom.hu ns2.ns0.hu	AS62214 Rackforest Zrt. AS62214 Rackforest Zrt.

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

716ms

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-18 11:40:03

Field	Value
Registrar	Gransy s.r.o.
Registered	2025-08-13
Expires	2027-08-12 (290d)

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

702ms

706ms

702ms

AAAA

836ms

TXT

3149ms

CAA

693ms

HTTPS

635ms

TLSA

599ms

SOA

35ms

MTA-STS

706ms

DNSSEC

716ms

SRV

837ms

Total

6938ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-08 06:39:40	6920ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-01 07:55:04	9021ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 03:37:10 shown	6938ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 13:21:18	14102ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 03:40:13	12093ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 03:26:42	2887ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 03:19:57	13203ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 02:58:29	2666ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 00:32:35	7839ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 23:13:50	7186ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 13:41:14	7875ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 22:25:05	8428ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 20:58:56	3518ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 07:09:39	13201ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 12:23:57	3193ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 05:38:15	6758ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 13:31:40	2773ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 23:40:40	5294ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 06:30:16	5716ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 01:45:20	14558ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 03:52:54	4552ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 03:09:55	3676ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 02:29:34	4690ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 02:24:01	7154ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 01:28:23	14868ms	2 NS 0 A 0 MX	❓ Unknown