3com.dk

📜 Historical scan 2026-07-30 17:56:25 · ← Latest scan

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

3com.dk is a registered .dk domain whose nameservers (ns1.hpe.com, ns2.hpe.com, ns3.hpe.com and 2 more) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 7 August 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#

5 records 4030ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.hpe.com	192.58.206.184	ns5.hpe.com	AS2165 HP Inc.
ns2.hpe.com	192.58.207.221	ns6.hpe.com	AS2165 HP Inc.
ns3.hpe.com	16.2.141.20	—	AS13013 Hewlett Packard France S.A.S.
ns4.hpe.com	16.2.138.125	iec01hpeibdns0a.ext.hpecore.net	AS13014 Hewlett Packard France S.A.S.
ns5.hpe.com	192.58.206.184	ns5.hpe.com	AS2165 HP 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#

10054ms

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-13 21:51:38

Field	Value
Registrar	MarkMonitor Inc.
Registered	2002-08-07
Expires	2027-09-30 (344d)

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

4030ms

4026ms

4032ms

AAAA

4028ms

TXT

20129ms

CAA

4028ms

HTTPS

4027ms

TLSA

4027ms

SOA

4031ms

MTA-STS

4036ms

DNSSEC

10054ms

SRV

4032ms

Total

49456ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-27 19:32:36	53203ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-23 22:33:51	40063ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-22 17:56:01	48569ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-21 17:47:40	65535ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-20 17:25:12	65535ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-19 12:42:27	24465ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-18 12:35:49	48032ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-16 14:45:45	40269ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-15 08:53:09	42536ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-13 03:24:43	20206ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-11 06:43:50	44713ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-10 05:15:08	44604ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-08 11:24:41	36350ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-31 23:23:47	19781ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-30 17:56:25 shown	49456ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-28 16:29:56	52624ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-27 13:37:30	63317ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-26 13:30:59	53445ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-25 13:17:11	41287ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-24 13:15:08	31458ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-23 11:46:45	61851ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-22 04:39:18	21224ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-20 22:42:44	39260ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-19 13:57:08	44790ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-18 11:07:23	29887ms	5 NS 0 A 0 MX	❓ Unknown