body-solution.dk

📜 Historical scan 2026-07-17 10:08:43 · ← Latest scan

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

body-solution.dk is a registered .dk domain whose nameservers (ns1.net-server.de, ns2.net-server.de) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 5 July 2002 (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#

2 records 264ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.net-server.de	2a02:420:0:3::3 87.237.124.6	dns01-ipv6.nbgo.de ns1.netbuild.net	AS38927 Net-Build GmbH AS38927 Net-Build GmbH
ns2.net-server.de	2a02:420:0:5::3 87.237.127.6	dns02-ipv6.nbgo.de ns2.netbuild.net	AS38927 Net-Build GmbH AS38927 Net-Build GmbH

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

332ms

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-13 16:13:32

Field	Value
Registrar	InterNetX GmbH
Registered	2002-07-05
Expires	2027-09-30 (347d)

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

264ms

263ms

AAAA

263ms

TXT

711ms

CAA

262ms

HTTPS

233ms

TLSA

105ms

SOA

28ms

MTA-STS

277ms

DNSSEC

332ms

SRV

890ms

Total

2644ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-23 20:19:45	11521ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 16:12:32	11521ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 04:23:13	5975ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 15:14:03	2464ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 15:00:41	7058ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 14:50:00	2449ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:17:43	6469ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 00:59:52	4153ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 16:53:09	11941ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 06:04:21	12235ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 01:21:28	4352ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 18:05:14	18373ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 16:42:23	4753ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 17:16:10	5844ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 23:28:39	12674ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 12:05:54	3588ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 11:37:07	19510ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 11:27:39	2941ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 10:49:00	12723ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 10:20:07	2819ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 09:45:57	2777ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 01:25:29	2670ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 17:43:40	10163ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 16:18:30	2820ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 10:08:43 shown	2644ms	2 NS 0 A 0 MX	❓ Unknown