verity.dk

📜 Historical scan 2026-07-22 21:36:28 · ← Latest scan

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

verity.dk is a registered .dk domain whose nameservers (byte.dns-parking.com, pixel.dns-parking.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 17 July 2026 (WHOIS) and first appeared in the .dk zone on 18 July 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 115ms

Nameserver	IP addresses	PTR	ASN / ISP
byte.dns-parking.com	172.64.53.67 2606:4700:5a::ac40:3543	byte.dns-parking.com byte.dns-parking.com	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.
pixel.dns-parking.com	172.64.52.230 2606:4700:52::ac40:34e6	pixel.dns-parking.com pixel.dns-parking.com	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.

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

265ms

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-19 02:09:55

Field	Value
Registrar	Realtime Register B.V.
Registered	2026-07-17
Expires	2027-07-16 (264d)

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

115ms

111ms

124ms

AAAA

136ms

TXT

540ms

CAA

110ms

HTTPS

124ms

TLSA

200ms

SOA

22ms

MTA-STS

500ms

DNSSEC

265ms

SRV

8153ms

Total

8966ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-21 07:34:01	3843ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 08:06:49	10771ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 13:09:39	16867ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 09:41:08	4667ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 09:33:26	6048ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 09:03:05	3530ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 05:51:36	2573ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 04:47:38	16992ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 04:22:30	9280ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 14:41:24	5753ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 09:12:46	2729ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 22:54:48	10755ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 11:14:37	3695ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 16:50:19	17078ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 00:28:16	17843ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 23:47:48	2779ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 23:13:30	11125ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 22:36:01	3139ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 21:57:20	1631ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 21:36:28 shown	8966ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 18:55:27	1664ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 14:39:02	1818ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 12:13:40	3166ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 08:42:25	4932ms	2 NS 0 A 0 MX	❓ Unknown