aalborgmtbshop.dk

📜 Historical scan 2026-07-25 11:01:48 · ← Latest scan

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

aalborgmtbshop.dk is a registered .dk domain whose nameservers (ns1.curanet.dk, ns2.curanet.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 7 October 2013 (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 300ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.curanet.dk	185.25.141.12 2a02:2339:4006:108::123	ns1.curanet.dk ns1.curanet.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.curanet.dk	2a02:2339:1:10f::123:123 91.197.248.75	ns2.curanet.dk ns2.curanet.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S

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

450ms

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-24 00:17:58

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2013-10-07
Expires	2027-10-31 (372d)

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

300ms

84ms

294ms

AAAA

118ms

TXT

524ms

CAA

347ms

HTTPS

295ms

TLSA

72ms

SOA

41ms

MTA-STS

131ms

DNSSEC

450ms

SRV

155ms

Total

1161ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-03 15:56:18	871ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-01 11:17:37	1055ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 22:24:27	1716ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 21:26:35	3343ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 21:24:20	5835ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 21:15:17	6998ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 20:49:27	5391ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 20:42:33	1719ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 06:39:02	1584ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 23:19:31	10031ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 21:30:01	3101ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 02:24:40	9999ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 01:10:32	3065ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 14:09:43	1221ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 09:44:55	1180ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 06:54:34	1724ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 10:17:01	2424ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 11:28:39	1038ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 11:06:50	1130ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 11:01:48 shown	1161ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 10:32:46	1853ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 05:53:07	17017ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 22:04:53	1503ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 16:40:28	2806ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 13:17:54	9856ms	2 NS 0 A 0 MX	❓ Unknown