aalborg-hoejtryk.dk

📜 Historical scan 2026-08-16 02:40:56 · ← Latest scan

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

aalborg-hoejtryk.dk is a registered .dk domain whose nameservers (ns1.danaweb.org, ns2.danaweb.org, ns3.danaweb.org and 1 more) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 19 July 2000 (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#

4 records 441ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.danaweb.org	185.25.141.12	ns1.curanet.dk	AS48854 team.blue Denmark A/S
ns2.danaweb.org	91.197.248.75	ns2.curanet.dk	AS48854 team.blue Denmark A/S
ns3.danaweb.org	185.25.141.12	ns1.curanet.dk	AS48854 team.blue Denmark A/S
ns4.danaweb.org	91.197.248.75	ns2.curanet.dk	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#

585ms

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-15 21:22:10

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2000-07-19
Expires	2027-09-30 (344d)

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

441ms

421ms

467ms

AAAA

448ms

TXT

1342ms

CAA

432ms

HTTPS

457ms

TLSA

231ms

SOA

306ms

MTA-STS

486ms

DNSSEC

585ms

SRV

488ms

Total

5443ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 16:49:03	1346ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-27 20:24:16	1248ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-24 12:35:12	2970ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-23 00:24:18	6376ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-22 00:21:59	1562ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-21 00:08:30	10263ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-19 23:51:58	3572ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-18 21:56:14	2307ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-17 10:57:44	2780ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-16 02:40:56 shown	5443ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-13 22:17:52	5874ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-12 19:04:55	3211ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-11 10:57:29	3563ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-10 01:36:43	2926ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-06 19:09:31	2606ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-03 00:45:41	2758ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-31 08:24:26	9052ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-29 03:13:53	9963ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:28:37	1031ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-26 22:58:03	1311ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-25 22:35:21	1186ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-24 22:22:01	1027ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-23 21:03:12	1159ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-22 20:26:12	2719ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-21 08:51:03	8731ms	4 NS 0 A 0 MX	❓ Unknown