secondwake.dk

📜 Historical scan 2026-07-28 23:10:55 · ← Latest scan

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

secondwake.dk is a registered .dk domain whose nameservers (ns01.000webhost.com, ns02.000webhost.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 4 August 2011 (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 4027ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.000webhost.com	153.92.2.6 2a02:4780::6	— —	AS47583 Hostinger International Limited AS47583 Hostinger International Limited
ns02.000webhost.com	153.92.2.7 2a02:4780::7	— —	AS47583 Hostinger International Limited AS47583 Hostinger International Limited

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

10061ms

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: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-13 20:16:06

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2011-08-04
Expires	2027-08-31 (317d)

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

4027ms

4030ms

AAAA

4029ms

TXT

20133ms

CAA

4028ms

HTTPS

4027ms

TLSA

22ms

SOA

4028ms

MTA-STS

4037ms

DNSSEC

10061ms

SRV

4032ms

Total

57260ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-20 14:10:50	63789ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 23:35:37	61356ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 23:22:19	63206ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 23:15:34	64465ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 23:09:41	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 22:44:38	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 22:22:09	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 09:24:16	57176ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 05:49:05	59003ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 20:53:04	60486ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 19:56:32	58741ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 08:10:31	62788ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 13:50:52	59389ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 12:49:16	61379ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 17:00:49	62914ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 03:11:19	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 21:09:07	61419ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 23:10:55 shown	57260ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 10:23:22	63314ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 09:58:42	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 09:28:56	62903ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 07:37:28	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 04:34:07	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 00:07:45	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 18:47:35	65535ms	2 NS 0 A 0 MX	❓ Unknown