kvikly.dk

Records from scan: 2026-08-23 05:23:44 · 65535ms total · last checked 2026-10-24 03:23 (unchanged)

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

kvikly.dk is a registered .dk domain whose nameservers (ns1pri.weboteket.dk, ns2dc1.weboteket.dk, ns3.weboteket.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was already in the .dk zone when our tracking began on 16 June 2026. Below are all of its DNS records from our latest scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.

🖥️ Nameservers#

3 records 1621ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1pri.weboteket.dk	157.250.160.82	ns1pri.weboteket.dk	AS3342 Cibicom A/S
ns2dc1.weboteket.dk	157.250.160.62	webhotel1.weboteket.dk	AS3342 Cibicom A/S
ns3.weboteket.dk	157.250.160.62	webhotel1.weboteket.dk	AS3342 Cibicom 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#

10194ms

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#

✗ No registration data yet — queued for a WHOIS lookup

📋 WHOIS#

⏱️ Lookup Timing#

1621ms

1619ms

1620ms

AAAA

1620ms

TXT

13402ms

CAA

1618ms

HTTPS

1614ms

TLSA

16041ms

SOA

100ms

MTA-STS

2232ms

DNSSEC

10194ms

SRV

16103ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-23 05:23:44 shown	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 05:13:16	63314ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 04:53:05	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 02:34:26	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 23:52:19	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 06:19:58	62503ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 04:14:59	63324ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 03:39:45	59962ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 17:37:55	57516ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 10:38:18	59247ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 12:38:42	64802ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-03 15:26:41	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-02 12:16:57	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 03:38:53	58498ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 02:47:19	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 02:31:55	57510ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 02:03:49	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 01:56:18	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 23:52:42	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 22:44:14	65502ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 14:28:52	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 12:42:43	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-19 02:39:36	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-18 01:33:53	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-16 10:47:29	65535ms	3 NS 0 A 0 MX	❓ Unknown