familiendamgaards.dk

Historical scan 2026-06-20 22:54:54  ·  ← Latest scan
Zone File Timeline & History Scan Now

familiendamgaards.dk is a .dk domain with no delegation in this scan. It was registered on 4 April 2003 (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#

No NS records found

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

Web & zone#

latest probe, not this scan · checked 2026-11-17 14:54:10
www178.72.21.249 (AS3342) (address records, no CNAME)
www vs bare domainSame network
familiendamgaards.dk: 178.72.21.249 (AS3342)
www.familiendamgaards.dk: 178.72.21.249 (AS3342)
WildcardNo

TLSA / DANE#

No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

DNSSEC#

441ms
CheckResult
Validation StatusNot applicable: the domain has no delegation, so there is no zone to validate (stored verdict: Unknown).
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsresolution failed: failure

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-11-11 07:07:56
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2003-04-04
Expires2027-04-30 (162d)

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#

NS
184ms
A
182ms
MX
179ms
AAAA
164ms
TXT
500ms
CAA
184ms
HTTPS
169ms
TLSA
17ms
SOA
195ms
MTA-STS
195ms
DNSSEC
441ms
SRV
208ms
Total
1160ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-17 14:54:10 295ms 2 NS 1 A 0 MX Insecure
2026-11-11 06:36:40 650ms 2 NS 1 A 0 MX Insecure
2026-11-05 20:22:09 461ms 2 NS 1 A 0 MX Insecure
2026-11-04 20:15:00 1776ms 2 NS 1 A 0 MX Insecure
2026-11-03 19:51:04 583ms 2 NS 1 A 0 MX Insecure
2026-11-02 15:12:52 307ms 2 NS 1 A 0 MX Insecure
2026-10-25 18:34:07 357ms 2 NS 1 A 0 MX Insecure
2026-10-24 10:50:39 1335ms 2 NS 1 A 0 MX Insecure
2026-10-15 14:58:57 733ms 2 NS 1 A 0 MX Insecure
2026-10-14 12:02:51 2229ms 2 NS 1 A 0 MX Insecure
2026-10-13 07:07:25 346ms 2 NS 1 A 0 MX Insecure
2026-10-12 04:51:15 353ms 2 NS 1 A 0 MX Insecure
2026-10-10 01:11:56 496ms 2 NS 1 A 0 MX Insecure
2026-10-02 21:57:23 525ms 2 NS 1 A 0 MX Insecure
2026-10-01 21:55:59 477ms 2 NS 1 A 0 MX Insecure
2026-09-20 06:43:32 490ms 2 NS 1 A 0 MX Insecure
2026-09-15 04:16:59 584ms 2 NS 1 A 0 MX Insecure
2026-09-05 06:21:25 408ms 2 NS 1 A 0 MX Insecure
2026-08-17 04:19:45 2898ms 2 NS 1 A 0 MX Insecure
2026-08-12 06:55:46 1340ms 2 NS 1 A 0 MX Insecure
2026-08-07 11:52:51 9442ms 2 NS 1 A 0 MX Insecure
2026-08-03 10:20:54 563ms 2 NS 1 A 0 MX Insecure
2026-07-26 21:54:33 510ms 2 NS 1 A 0 MX Insecure
2026-07-25 21:49:12 8465ms 2 NS 1 A 0 MX Insecure
2026-07-23 19:25:43 891ms 2 NS 1 A 0 MX Insecure