feriehuset-boernegaarden.dk
Historical scan 2026-07-03 01:13:14 · ← Latest scan
feriehuset-boernegaarden.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 3 May 2022 (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 4030msA 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
Web & zone#
latest probe, not this scan · checked 2026-10-25 06:32:10| www CNAME | ghs.googlehosted.com (all on googlehosted.com) |
| www vs bare domain | Different networks feriehuset-boernegaarden.dk: 195.47.247.18 (AS51468) (all like this)www.feriehuset-boernegaarden.dk: 142.251.143.147 2a00:1450:400f:802::2013 (AS15169) |
| Wildcard | No |
| Denial of existence | NSEC3 · 0 iterations · no salt RFC 9276 ✓ |
| CDS / CDNSKEY | None 0 CDS, 0 CDNSKEY |
TLSA / DANE#
No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)
DNSSEC#
10092ms| Check | Result |
|---|---|
| Validation Status | Unknown (the delegated nameservers don't answer) |
| AD Flag (resolver validates) | Not set |
| DS Record | Found |
| DNSKEY Record | Not found |
| Flags | resolution failed: timed out |
SOA#
No SOA record found
Registration#
WHOIS fetched 2026-11-13 10:06:24| Field | Value |
|---|---|
| Registrar | ONE.COM A/S |
| Registered | 2022-05-03 |
| Expires | 2027-05-02 (164d) |
Same registrant#
0 domainsOther .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#
NS
A
MX
AAAA
TXT
CAA
HTTPS
TLSA
SOA
MTA-STS
DNSSEC
SRV
Total
Scan History#
| Scanned At | Duration | Records | DNSSEC |
|---|---|---|---|
| 2026-10-25 06:32:10 | 343ms | 2 NS 1 A 1 MX | Secure |
| 2026-10-22 13:47:08 | 1476ms | 2 NS 1 A 1 MX | Secure |
| 2026-10-14 22:40:30 | 334ms | 2 NS 1 A 1 MX | Secure |
| 2026-10-13 22:10:06 | 327ms | 2 NS 1 A 1 MX | Secure |
| 2026-10-12 21:31:16 | 873ms | 2 NS 1 A 1 MX | Secure |
| 2026-09-30 12:20:13 | 448ms | 2 NS 1 A 1 MX | Secure |
| 2026-09-29 16:20:21 | 440ms | 2 NS 1 A 1 MX | Secure |
| 2026-09-17 09:58:40 | 679ms | 2 NS 1 A 1 MX | Secure |
| 2026-08-14 03:28:56 | 1754ms | 2 NS 1 A 1 MX | Secure |
| 2026-08-12 18:47:22 | 2541ms | 2 NS 1 A 1 MX | Secure |
| 2026-07-14 13:59:18 | 563ms | 2 NS 1 A 1 MX | Secure |
| 2026-07-03 01:13:14 shown | 16805ms | 2 NS 0 A 0 MX | Unknown |
| 2026-06-23 09:18:30 | 596ms | 2 NS 1 A 1 MX | Secure |
| 2026-06-21 09:55:18 | 354ms | 2 NS 1 A 1 MX | Secure |
| 2026-06-17 10:17:52 | 3127ms | 2 NS 1 A 0 MX | Secure |
| 2026-06-17 10:06:57 | 501ms | 2 NS 1 A 0 MX | Secure |