aabenraabridgecenter.dk

📜 Historical scan 2026-07-24 17:24:46 · ← Latest scan

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

aabenraabridgecenter.dk is a registered .dk domain whose nameservers (ns1.dns-123.net, ns2.dns-123.net, ns3.dns-123.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 4 September 2007 (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 125ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.dns-123.net	35.198.132.83	83.132.198.35.bc.googleusercontent.com	AS396982 Google LLC
ns2.dns-123.net	35.187.184.173	173.184.187.35.bc.googleusercontent.com	AS396982 Google LLC
ns3.dns-123.net	35.228.54.1	1.54.228.35.bc.googleusercontent.com	AS396982 Google LLC

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

181ms

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-27 01:13:06

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2007-09-04
Expires	2027-09-30 (338d)

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

125ms

113ms

2030ms

AAAA

123ms

TXT

719ms

CAA

124ms

HTTPS

107ms

TLSA

174ms

SOA

34ms

MTA-STS

153ms

DNSSEC

181ms

SRV

10450ms

Total

11637ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 09:28:38	5245ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-27 23:14:19	7991ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-08 19:10:24	14988ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-24 05:30:07	12715ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 01:32:21	2304ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 01:24:40	5764ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 01:21:22	11097ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 00:31:51	9128ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 00:20:21	10145ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 22:57:42	9947ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 11:18:17	8689ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 06:29:38	12731ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 22:35:27	5983ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 22:15:03	9644ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 11:36:16	12742ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 10:00:37	7378ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 07:48:04	5479ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-06 01:48:58	8869ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-03 11:45:51	17005ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 01:22:54	5531ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 19:22:35	17257ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 18:07:22	5544ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 17:44:29	12541ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 17:24:46 shown	11637ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 17:07:50	4368ms	3 NS 0 A 0 MX	❓ Unknown