beerkroket.dk

📜 Historical scan 2026-08-24 08:48:52 · ← Latest scan

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

beerkroket.dk is a registered .dk domain whose nameservers (ns1.nameservices.us, ns2.nameservices.us) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 6 April 2006 (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 42ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.nameservices.us	—	—	—
ns2.nameservices.us	—	—	—

🌍 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

🧩 Web & zone#

latest probe, not this scan · checked 2026-10-02 15:16:21

www	Address record (no CNAME)
Wildcard	Yes: any name under the zone resolves

🔗 TLSA / DANE#

✗ No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

🔐 DNSSEC#

2086ms

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-11 15:41:49

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2006-04-06
Expires	2027-04-30 (191d)

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

42ms

2040ms

4052ms

AAAA

4036ms

TXT

10140ms

CAA

4036ms

HTTPS

4042ms

TLSA

4027ms

SOA

42ms

MTA-STS

59ms

DNSSEC

2086ms

SRV

4062ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-09 10:41:09	949ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-05 15:30:46	1124ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-02 15:16:21	3372ms	2 NS 1 A 1 MX	🔓 Insecure
2026-10-01 15:13:17	2595ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-30 15:02:57	4247ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-29 14:55:28	3450ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-28 14:52:08	3352ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-27 14:44:47	3252ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-26 14:34:25	3246ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-25 14:25:26	3191ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-24 14:11:45	4361ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-23 13:47:16	10001ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-14 21:06:01	6185ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-07 19:57:17	3536ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-03 21:28:52	12856ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-31 11:53:23	3468ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-30 05:38:11	3671ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-28 11:33:03	3178ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-27 11:26:08	3123ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-26 10:16:51	10450ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-24 08:48:52 shown	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 07:24:16	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 07:09:51	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 07:03:05	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 06:18:40	65535ms	2 NS 0 A 0 MX	❓ Unknown