nicolaschoice.dk

📜 Historical scan 2026-08-24 07:22:01 · ← Latest scan

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

nicolaschoice.dk is a registered .dk domain whose nameservers (ns1.rochendns.com, ns2.rochendns.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 18 September 2014 (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 285ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.rochendns.com	2600:1f16:20f:500:7e3:deb3:3b12:4ae7 52.223.14.62	— a9a9413da7e6bd94f.awsglobalaccelerator.com	AS16509 Amazon.com, Inc. AS16509 Amazon.com, Inc.
ns2.rochendns.com	2a05:d018:97c:5000:3519:a42d:e3ae:5a73 35.71.133.51	— a9a9413da7e6bd94f.awsglobalaccelerator.com	AS16509 Amazon.com, Inc. AS16509 Amazon.com, 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#

307ms

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-19 17:52:26

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2014-09-18
Expires	2027-09-30 (343d)

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

285ms

244ms

285ms

AAAA

299ms

TXT

3016ms

CAA

131ms

HTTPS

283ms

TLSA

139ms

SOA

28ms

MTA-STS

1083ms

DNSSEC

307ms

SRV

1468ms

Total

4105ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-25 10:52:58	5639ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 07:22:01 shown	4105ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 06:35:48	5467ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 06:14:59	8481ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 06:04:09	11776ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 05:12:56	3478ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 04:42:03	8009ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 11:30:31	7584ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 10:37:08	8083ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 21:05:35	6509ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 10:56:50	5881ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 00:22:20	14638ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 08:11:01	7617ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 07:26:33	8333ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 15:50:23	5538ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 18:21:31	12581ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 17:25:38	5254ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 17:08:59	10930ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 16:38:40	5318ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 14:09:54	12453ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 11:42:10	5266ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 06:16:10	12575ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 04:55:38	3597ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 22:37:13	4682ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 21:23:18	6131ms	2 NS 0 A 0 MX	❓ Unknown