vivi-juul.dk

📜 Historical scan 2026-07-05 02:07:13 · ← Latest scan

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

vivi-juul.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 2 April 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 4318ms

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#

10348ms

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-27 04:31:17

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2013-04-02
Expires	2027-04-30 (184d)

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

4318ms

4291ms

4307ms

AAAA

4323ms

TXT

18433ms

CAA

4208ms

HTTPS

4250ms

TLSA

4021ms

SOA

4265ms

MTA-STS

4331ms

DNSSEC

10348ms

SRV

4328ms

Total

35716ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 01:42:50	1258ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-31 18:15:55	2592ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 15:25:04	3797ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 12:40:44	1602ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 12:27:44	28460ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 12:11:37	2097ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 10:40:27	4856ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 10:38:01	778ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 02:32:54	8926ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 13:31:23	10219ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 11:41:39	1506ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 16:43:56	10159ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 13:15:43	4213ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 06:59:34	1673ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 05:52:25	10049ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 10:52:36	1423ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 10:35:08	2892ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 10:13:06	1432ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 07:29:09	8768ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 06:45:37	865ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 23:57:36	8988ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 13:24:03	1064ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 23:59:04	24955ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 22:59:56	10036ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-15 10:59:01	1471ms	2 NS 0 A 0 MX	❓ Unknown