infrastructuresecurity.dk

📜 Historical scan 2026-07-25 04:08:52 · ← Latest scan

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

infrastructuresecurity.dk is a registered .dk domain whose nameservers (ns1.dnsdomene.net, ns2.dnsdomene.net, ns3.dnsdomene.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 21 November 2024 (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 68ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.dnsdomene.net	185.215.199.252	ns1.dnsdomene.net	AS61207 Hostek AB
ns2.dnsdomene.net	217.170.194.27	ns2.dnsdomene.net	AS34989 ServeTheWorld AS
ns3.dnsdomene.net	212.16.184.125	ns3.dnsdomene.net	AS61207 Hostek AB

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

126ms

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-14 17:49:15

Field	Value
Registrar	Name SRS AB
Registered	2024-11-21
Expires	2026-11-20 (30d)

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

68ms

71ms

66ms

AAAA

63ms

TXT

358ms

CAA

92ms

HTTPS

57ms

TLSA

66ms

SOA

35ms

MTA-STS

145ms

DNSSEC

126ms

SRV

261ms

Total

1088ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-24 05:05:15	11483ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-05 13:05:30	12426ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 20:12:59	6535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 15:59:52	8383ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 15:57:30	6828ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 15:56:06	11792ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 12:54:30	4633ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 12:50:14	3508ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 11:39:41	5076ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 10:23:17	1405ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 01:14:35	5963ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 00:59:11	3512ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 21:24:27	3210ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 07:00:16	6260ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 02:35:40	3302ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-06 15:03:49	3766ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-03 08:43:55	9865ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-01 00:04:11	9444ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 11:34:06	11213ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 05:31:24	11453ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 05:10:15	1104ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 04:37:01	9221ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 04:08:52 shown	1088ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 03:36:57	11307ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 02:30:02	1490ms	3 NS 0 A 0 MX	❓ Unknown