vor-alliance.dk

📜 Historical scan 2026-07-28 08:27:23 · ← Latest scan

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

vor-alliance.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 4 July 2016 (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 4029ms

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#

9161ms

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-23 19:04:23

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2016-07-04
Expires	2027-07-31 (278d)

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

4029ms

117ms

4029ms

AAAA

4028ms

TXT

4491ms

CAA

2117ms

HTTPS

4028ms

TLSA

2117ms

SOA

25ms

MTA-STS

2126ms

DNSSEC

9161ms

SRV

4029ms

Total

14357ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 01:48:21	1334ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-09-15 16:46:36	39033ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-23 22:39:02	1169ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-22 21:55:06	1476ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-21 21:44:56	30426ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 21:43:31	1816ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-19 21:27:08	11339ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-18 20:54:02	2847ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-17 03:59:06	1065ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-15 22:48:16	1239ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-14 18:07:49	10159ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-10 21:58:38	2564ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-09 21:38:02	1517ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-06 23:40:42	879ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-28 08:27:23 shown	14357ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 06:13:50	8728ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-26 05:53:19	1103ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-25 05:39:12	765ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-24 03:39:15	959ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-22 22:56:52	974ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-21 22:14:19	1170ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-20 01:00:40	27258ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 22:31:01	1115ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-17 20:38:28	8749ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-13 05:28:36	1083ms	2 NS 0 A 0 MX	⚠️ Bogus