husavisen.dk

📜 Historical scan 2026-08-17 03:37:02 · ← Latest scan

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

husavisen.dk is a registered .dk domain whose nameservers (ns1.dnsresolve.io, ns2.dnsresolve.eu, ns3.dnsresolve.me) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 21 July 2026 (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 627ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.dnsresolve.io	172.105.72.183 2a01:7e01::f03c:94ff:fe6a:805d	ns1.dnsresolve.io —	AS63949 Akamai Connected Cloud AS63949 Akamai Connected Cloud
ns2.dnsresolve.eu	152.115.36.124	—	AS31027 GlobalConnect A/S
ns3.dnsresolve.me	212.71.233.109 2a01:7e00::f03c:94ff:fe9f:2cca	212-71-233-109.ip.linodeusercontent.com —	AS63949 Akamai Connected Cloud AS63949 Akamai Connected Cloud

🌍 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

🧩 Web & zone#

latest probe, not this scan · checked 2026-10-08 16:17:23

www CNAME	husavisen.dk (all on husavisen.dk) → 152.115.50.2 (AS31027)
www vs bare domain	Same network husavisen.dk: 152.115.50.2 (AS31027) www.husavisen.dk: 152.115.50.2 (AS31027)
Wildcard	No

✍️ DKIM keys#

1 found

Selector	CNAME	Key
default	—	RSA · ~2048 bit

DKIM selectors can't be listed, so we check the common ones (Microsoft 365, Google, Mailchimp, SendGrid, generic). Keys under other selectors aren't shown.

🔗 TLSA / DANE#

✗ No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

🔐 DNSSEC#

9671ms

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-08 00:23:26

Field	Value
Registrar	STANDOUT A/S
Registered	2026-07-21
Expires	2027-07-20 (267d)

📋 WHOIS#

⏱️ Lookup Timing#

627ms

626ms

AAAA

606ms

TXT

3102ms

CAA

610ms

HTTPS

620ms

TLSA

629ms

SOA

621ms

MTA-STS

618ms

DNSSEC

9671ms

SRV

679ms

Total

12866ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 14:28:31	520ms	3 NS 1 A 1 MX	🔓 Insecure
2026-09-18 06:14:17	1622ms	3 NS 1 A 1 MX	🔓 Insecure
2026-08-27 03:02:54	6268ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-25 22:20:48	6323ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-24 08:20:46	6176ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 05:36:56	8232ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 05:22:17	2247ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 04:53:52	6253ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 03:24:30	5872ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 02:59:53	6621ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 03:37:02 shown	12866ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 21:56:32	5667ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 19:19:57	5519ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 03:53:44	6030ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 02:26:04	13107ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 06:34:58	6330ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-08 03:54:00	5866ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 03:39:21	4809ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-30 09:03:29	30060ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 07:36:37	12551ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 20:43:12	2578ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 19:53:07	2523ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 19:16:32	6427ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 18:46:24	3523ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 13:55:48	11421ms	3 NS 0 A 0 MX	❓ Unknown