nhsolution.dk

📜 Historical scan 2026-07-04 09:45:02 · ← Latest scan

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

nhsolution.dk is a registered .dk domain whose nameservers (ns1.ipage.com, ns2.ipage.com) do not answer for it, so it is currently a lame delegation and does not resolve. It 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 2040ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.ipage.com	66.96.142.116 66.96.142.162 66.96.142.163	116.142.96.66.static.eigbox.net ns1.ipage.com ns1.ipage.com	AS29873 Newfold Digital, Inc. AS29873 Newfold Digital, Inc. AS29873 Newfold Digital, Inc.
ns2.ipage.com	65.254.254.151	65-254-254-151.yourhostingaccount.com	AS29873 Newfold Digital, Inc.

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

2514ms

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#

✗ No registration data yet — queued for a WHOIS lookup

📋 WHOIS#

⏱️ Lookup Timing#

2040ms

2047ms

2034ms

AAAA

2034ms

TXT

10092ms

CAA

2018ms

HTTPS

2019ms

TLSA

2018ms

SOA

2031ms

MTA-STS

2023ms

DNSSEC

2514ms

SRV

4033ms

Total

18570ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-23 13:58:53	28853ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 11:06:03	10430ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 10:49:58	37406ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 09:38:44	14166ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:38:47	8069ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 07:05:56	34608ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 07:39:58	35719ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 01:28:52	35589ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 09:37:08	35865ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 08:17:32	35673ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 11:51:20	35771ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 16:48:58	16469ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 14:40:54	22959ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 14:08:12	5986ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 13:18:23	6552ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 13:02:50	5488ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 09:59:48	8923ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 06:14:02	8641ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 23:18:55	35910ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 10:43:55	35807ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 08:27:25	5144ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 07:51:09	8020ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-15 16:09:35	34511ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-14 04:20:15	7529ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-12 09:45:34	7345ms	2 NS 0 A 0 MX	❓ Unknown