visualiseit.dk

📜 Historical scan 2026-07-06 14:59:10 · ← Latest scan

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

visualiseit.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 February 2004 (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 8147ms

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#

16081ms

Check	Result
Validation Status	❓ Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates)	✗ Not set
DS Record	✓ Found
DNSKEY Record	✗ Not found
Flags	resolution failed: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-27 15:42:50

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2004-02-03
Expires	2027-02-28 (123d)

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

8147ms

16062ms

8140ms

AAAA

16061ms

TXT

8388ms

CAA

8086ms

HTTPS

8136ms

TLSA

64ms

SOA

16057ms

MTA-STS

8099ms

DNSSEC

16081ms

SRV

16060ms

Total

35894ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-24 23:16:18	27146ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-21 09:41:03	3104ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-23 18:57:45	3218ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-22 14:24:57	5528ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-21 14:03:42	5483ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-20 13:48:31	5860ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-19 11:00:37	6855ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-18 10:56:58	2852ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-17 05:16:51	2304ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-16 05:06:34	10194ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-14 20:51:40	3777ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-13 10:01:50	4769ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-11 19:16:56	29351ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 01:27:59	9060ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-07 10:37:35	8860ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-05 08:42:01	1433ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-04 07:13:58	51294ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 18:50:54	838ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-30 14:07:35	53449ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 06:09:58	1336ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-27 05:44:44	1266ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-26 05:10:44	10026ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-25 04:57:32	2808ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-24 04:32:26	1104ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-23 04:13:09	2921ms	2 NS 0 A 0 MX	⚠️ Bogus