vrogumsmed.dk

📜 Historical scan 2026-07-18 16:04:31 · ← Latest scan

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

vrogumsmed.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 3 October 2013 (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 168ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.one.com	195.206.121.10 2001:67c:28cc::10	ns01.one.com ns01.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns02.one.com	185.10.11.10 2001:67c:3c0::10	ns02.one.com ns02.one.com	AS51468 One.com A/S AS51468 One.com 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#

198ms

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-26 11:18:37

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2013-10-03
Expires	2027-10-31 (369d)

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

168ms

127ms

171ms

AAAA

130ms

TXT

589ms

CAA

166ms

HTTPS

164ms

TLSA

120ms

SOA

23ms

MTA-STS

139ms

DNSSEC

198ms

SRV

170ms

Total

1386ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-03 14:56:02	10128ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 01:48:08	10075ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 20:27:55	2703ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 13:48:59	6373ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 13:14:09	980ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 12:37:53	1309ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:13:04	2499ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 06:43:44	3215ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 14:30:47	2562ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 08:26:01	1253ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 09:39:50	1505ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 21:08:29	1079ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 12:52:13	925ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 05:32:47	10084ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 10:13:33	1114ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 07:33:23	1406ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 09:29:28	792ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 08:52:06	10076ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 09:48:29	989ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 09:38:34	1091ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 09:05:36	16722ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 07:08:47	968ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 04:08:45	16805ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 02:04:55	933ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 22:30:40	8999ms	2 NS 0 A 0 MX	❓ Unknown