hj-multiservice.dk

📜 Historical scan 2026-08-20 12:13:48 · ← Latest scan

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

hj-multiservice.dk is a registered .dk domain whose nameservers (ns2.vpweb.com, ns3.vpweb.com, ns4.vpweb.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 23 May 2014 (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 4359ms

Nameserver	IP addresses	PTR	ASN / ISP
ns2.vpweb.com	52.4.205.198	ec2-52-4-205-198.compute-1.amazonaws.com	AS14618 Amazon.com, Inc.
ns3.vpweb.com	34.246.26.49	ec2-34-246-26-49.eu-west-1.compute.amazonaws.com	AS16509 Amazon.com, Inc.
ns4.vpweb.com	34.234.174.79	ec2-34-234-174-79.compute-1.amazonaws.com	AS14618 Amazon.com, 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#

10619ms

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-16 19:10:14

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2014-05-23
Expires	2027-05-31 (226d)

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

4359ms

4378ms

4375ms

AAAA

4328ms

TXT

16986ms

CAA

4359ms

HTTPS

4377ms

TLSA

4043ms

SOA

4347ms

MTA-STS

4439ms

DNSSEC

10619ms

SRV

4398ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 14:46:04	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-30 01:08:42	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-26 09:34:45	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-12 03:41:08	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-27 04:50:30	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 14:59:02	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 13:11:59	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 12:37:30	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 12:13:48 shown	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 04:02:30	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 03:07:43	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 10:02:24	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 21:44:07	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 07:34:21	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 02:12:51	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 19:45:11	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-08 09:36:33	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-06 02:20:45	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-31 07:17:14	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 16:02:54	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 15:14:46	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 14:44:38	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 14:26:35	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 11:00:11	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 09:50:37	65535ms	3 NS 0 A 0 MX	❓ Unknown