medcom1-4.dk

📜 Historical scan 2026-07-06 12:39:21 · ← Latest scan

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

medcom1-4.dk is a registered .dk domain whose nameservers (ns1.incaptiva.dk, ns2.incaptiva.dk, ns3.incaptiva.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 7 March 2006 (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 8035ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.incaptiva.dk	94.231.103.59	linux117.unoeuro.com	AS48854 team.blue Denmark A/S
ns2.incaptiva.dk	94.231.103.59	linux117.unoeuro.com	AS48854 team.blue Denmark A/S
ns3.incaptiva.dk	94.231.103.59	linux117.unoeuro.com	AS48854 team.blue Denmark A/S

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

16087ms

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: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-20 07:23:25

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2006-03-07
Expires	2027-03-31 (161d)

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

8035ms

16023ms

8037ms

AAAA

16040ms

TXT

8088ms

CAA

8032ms

HTTPS

9066ms

TLSA

16ms

SOA

1065ms

MTA-STS

8056ms

DNSSEC

16087ms

SRV

16054ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-23 05:59:06	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 05:33:52	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 05:21:15	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 04:10:15	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 02:22:08	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 10:24:13	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 06:04:43	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 07:47:04	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 07:33:04	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 05:40:54	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-08 09:39:00	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-06 22:28:56	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-01 19:27:45	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 15:52:41	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 15:23:05	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 15:11:44	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 14:34:46	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 13:08:51	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 06:16:18	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 05:17:35	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-18 23:49:15	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-17 21:44:43	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-16 18:44:33	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-11 20:11:50	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-10 14:53:29	65535ms	3 NS 0 A 0 MX	❓ Unknown