viskaberdetsammen.dk

📜 Historical scan 2026-08-10 05:15:37 · ← Latest scan

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

viskaberdetsammen.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 7 August 2024 (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 52ms

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#

129ms

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-27 14:09:21

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2024-08-07
Expires	2027-08-06 (282d)

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

52ms

56ms

46ms

AAAA

38ms

TXT

8308ms

CAA

45ms

HTTPS

56ms

TLSA

45ms

SOA

28ms

MTA-STS

59ms

DNSSEC

129ms

SRV

139ms

Total

8928ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-27 11:21:13	1903ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-03 04:43:08	1304ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 02:00:48	808ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 16:19:22	1195ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 16:10:57	1211ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 15:51:04	1924ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 08:15:01	10888ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 08:12:53	807ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 07:00:50	932ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 01:03:08	16232ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 21:00:04	3053ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 19:33:38	1546ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 17:21:10	2735ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 05:15:37 shown	8928ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 19:38:55	1436ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 18:03:51	1447ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 13:24:01	26008ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 03:30:30	10030ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 03:07:41	849ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 02:44:59	836ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 02:11:55	849ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 00:29:32	10091ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 22:29:33	8645ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 19:27:26	2812ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 18:36:44	8647ms	2 NS 0 A 0 MX	❓ Unknown