viaselect.dk

📜 Historical scan 2026-07-27 09:22:53 · ← Latest scan

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

viaselect.dk is a registered .dk domain whose nameservers (nsauth1.bit.nl, nsauth2.bit.nl) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 16 August 2006 (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 106ms

Nameserver	IP addresses	PTR	ASN / ISP
nsauth1.bit.nl	2001:7b8:3:2c::53 213.136.12.51	nsauth1.bit.nl nsauth1.bit.nl	AS12859 BIT BV AS12859 BIT BV
nsauth2.bit.nl	2001:7b8:3:2d::53 213.136.12.59	nsauth2.bit.nl nsauth2.bit.nl	AS12859 BIT BV AS12859 BIT BV

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

289ms

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-12 04:20:53

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2006-08-16
Expires	2027-08-31 (317d)

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

106ms

265ms

185ms

AAAA

200ms

TXT

818ms

CAA

145ms

HTTPS

184ms

TLSA

129ms

SOA

33ms

MTA-STS

214ms

DNSSEC

289ms

SRV

647ms

Total

2118ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-18 00:53:16	11711ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 06:28:54	2225ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 01:57:27	3195ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 01:54:35	1845ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 01:50:48	6022ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 00:11:20	4217ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 21:06:52	5402ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 11:35:59	6608ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 02:10:21	6876ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 23:20:46	3801ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 18:03:08	4765ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 17:53:27	11753ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 01:48:56	4655ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 05:07:16	3927ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 17:49:07	1879ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 05:12:34	1791ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 09:22:53 shown	2118ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 09:08:55	1737ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 08:28:49	1900ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 08:11:48	4516ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 07:40:30	2611ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 04:29:12	3183ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 01:41:45	3688ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 13:04:28	3754ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 23:27:25	2391ms	2 NS 0 A 0 MX	❓ Unknown