optimize-courier.dk

📜 Historical scan 2026-08-18 21:01:02 · ← Latest scan

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

optimize-courier.dk is a registered .dk domain whose nameservers (ns1.instradns.com, ns2.instradns.com, ns3.instradns.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 23 October 2017 (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#

3 records 4218ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.instradns.com	75.2.6.34	aef93cd39153ffbac.awsglobalaccelerator.com	AS16509 Amazon.com, Inc.
ns2.instradns.com	75.2.85.37	a9bf3e392db71e4d0.awsglobalaccelerator.com	AS16509 Amazon.com, Inc.
ns3.instradns.com	99.83.188.20	aef93cd39153ffbac.awsglobalaccelerator.com	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#

10405ms

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-18 20:32:09

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2017-10-23
Expires	2026-10-31 (10d)

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

4218ms

4239ms

4266ms

AAAA

4200ms

TXT

14955ms

CAA

4205ms

HTTPS

4242ms

TLSA

755ms

SOA

269ms

MTA-STS

4508ms

DNSSEC

10405ms

SRV

4279ms

Total

54629ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 10:14:03	38568ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-28 06:31:43	29583ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-24 01:37:11	3650ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 23:53:37	9866ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 23:46:45	2707ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 23:43:45	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 21:48:17	2823ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 21:01:02 shown	54629ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 14:56:59	55147ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 16:46:58	59164ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 23:10:59	46922ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 02:58:25	2431ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 08:42:59	59317ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-06 16:21:15	50551ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-03 21:20:16	39532ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-02 09:03:22	9433ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 06:08:08	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 05:30:20	3739ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 05:10:11	24703ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 03:34:08	2667ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 01:59:28	4262ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 17:24:08	4667ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 16:53:08	35876ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-19 16:46:06	50165ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-18 12:46:09	17520ms	3 NS 0 A 0 MX	❓ Unknown