kingjanuary.dk

📜 Historical scan 2026-09-14 02:31:31 · ← Latest scan

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

kingjanuary.dk is a registered .dk domain whose nameservers (ns1.crazydomains.com, ns2.crazydomains.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 9 June 2019 (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 1133ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.crazydomains.com	162.159.24.7 2400:cb00:2049:1::a29f:1807	— e.ns.zerigo.net	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.
ns2.crazydomains.com	162.159.25.129 2400:cb00:2049:1::a29f:1981	— ns3.linode.com	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.

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

9196ms

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-21 10:10:28

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2019-06-09
Expires	2027-06-30 (247d)

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

1133ms

767ms

939ms

AAAA

1072ms

TXT

4878ms

CAA

961ms

HTTPS

1048ms

TLSA

765ms

SOA

44ms

MTA-STS

1133ms

DNSSEC

9196ms

SRV

1167ms

Total

13350ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-08 17:57:18	10140ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 02:35:14	7756ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-26 03:02:12	12349ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-14 02:31:31 shown	13350ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 09:40:33	12915ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 09:15:34	14806ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 08:58:42	13636ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 08:10:40	5856ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:17:49	10687ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 06:05:29	10340ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 00:17:33	12776ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 22:06:29	5337ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 06:05:01	9481ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 01:34:35	11626ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 21:54:26	3965ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 17:29:30	26448ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 00:25:56	12828ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 13:38:17	9404ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 02:58:40	5022ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 12:12:06	12122ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 06:40:10	12850ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 05:53:30	7233ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 05:17:18	8286ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 04:22:45	9403ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 03:45:37	7395ms	2 NS 0 A 0 MX	❓ Unknown