defibsolutions.dk

📜 Historical scan 2026-08-02 08:48:32 · ← Latest scan

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

defibsolutions.dk is a registered .dk domain whose nameservers (ns.eatserver.nl, ns2.eatserver.nl) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 28 November 2018 (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 741ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.eatserver.nl	2001:1460:3:4:1c00:aeff:fe00:2715 62.221.202.210	ns.eatserver.nl ns.eatserver.nl	AS48635 Your Hosting B.V. AS48635 Your Hosting B.V.
ns2.eatserver.nl	195.20.11.100 2001:1460:2:0:1c21:e9ff:fe00:1b6	ns2.eatserver.nl ns2.eatserver.nl	AS48635 Your Hosting B.V. AS48635 Your Hosting B.V.

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

16059ms

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 05:58:35

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2018-11-28
Expires	2026-11-30 (44d)

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

741ms

16045ms

16040ms

AAAA

16043ms

TXT

1412ms

CAA

419ms

HTTPS

413ms

TLSA

123ms

SOA

33ms

MTA-STS

243ms

DNSSEC

16059ms

SRV

2114ms

Total

17018ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-24 05:09:36	22968ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-22 18:50:31	23087ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 07:33:02	17787ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 04:32:36	21883ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 04:14:43	3345ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 03:56:55	9821ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 03:24:54	20616ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 02:11:43	12841ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 20:29:47	18508ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 06:07:36	21235ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 05:41:13	19941ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 05:02:04	16706ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 01:21:31	17555ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 17:48:39	15586ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 10:11:40	8576ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 08:48:32 shown	17018ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 17:28:06	3063ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 15:12:32	21266ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 12:53:31	21823ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 09:15:17	11571ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 07:48:12	27000ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 07:20:04	10333ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 06:39:09	3197ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 02:29:51	2508ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 23:34:57	9814ms	2 NS 0 A 0 MX	❓ Unknown