valsgaardforsamlingshus.dk

📜 Historical scan 2026-08-19 16:21:00 · ← Latest scan

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

valsgaardforsamlingshus.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 22 August 2019 (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 201ms

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#

2087ms

Check	Result
Validation Status	⚠️ Bogus — the parent still publishes a DS record, but the delegated nameservers don't answer, so no signed answer can be fetched. The zone isn't serving broken signatures; it isn't serving at all.
AD Flag (resolver validates)	✗ Not set
DS Record	✓ Found
DNSKEY Record	✗ Not found
Flags	resolution failed: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-09 09:49:20

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2019-08-22
Expires	2027-08-31 (308d)

📋 WHOIS#

⏱️ Lookup Timing#

201ms

185ms

144ms

AAAA

125ms

TXT

687ms

CAA

145ms

HTTPS

203ms

TLSA

119ms

SOA

62ms

MTA-STS

215ms

DNSSEC

2087ms

SRV

206ms

Total

2904ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-25 15:35:51	1777ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-10-09 11:30:14	1232ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-23 21:24:03	3538ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-22 19:59:05	4733ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-21 19:55:30	1559ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-20 19:38:34	7481ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-19 16:21:00 shown	2904ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-18 16:19:43	1070ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-17 12:24:25	16918ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-16 04:25:48	1589ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-15 01:37:38	2422ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-13 22:34:34	4257ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-12 19:24:45	1538ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-11 03:03:39	8851ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-10 00:28:22	10143ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-05 13:25:27	2607ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-27 17:31:00	10068ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-26 17:03:19	1406ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-25 16:43:41	910ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-24 16:19:32	1015ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-23 16:00:01	2367ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-22 14:59:16	1007ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-21 14:18:10	774ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-20 02:37:08	10054ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-18 16:18:16	24869ms	2 NS 0 A 0 MX	⚠️ Bogus