loefbergsogfenningsfond.dk

Historical scan 2026-08-21 02:25:42  ·  ← Latest scan
Deactivated by the registry Zone File Timeline & History Scan Now

loefbergsogfenningsfond.dk is a .dk domain the registry has taken out of service: it is delegated to the registry's own sentinel nameservers (nonexistent.punktum.dk), so it does not resolve. It was registered on 1 July 2021 (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#

1 records   369ms
NameserverIP addressesPTRASN / ISP
nonexistent.punktum.dk — — —

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-01 01:20:33
www CNAMEcdn3.wixdns.net (all on wixdns.net)
www vs bare domainDifferent networks
loefbergsogfenningsfond.dk: 185.230.63.107 185.230.63.171 185.230.63.186 (AS58182)
www.loefbergsogfenningsfond.dk: 162.159.143.12 172.66.3.8 (AS13335)
(all like this)
WildcardNo

TLSA / DANE#

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

DNSSEC#

664ms
CheckResult
Validation Status Unknown (the delegated nameservers don't answer)
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-10-26 06:59:36
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2021-07-01
Expires2027-07-31 (254d)

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
369ms
A
367ms
MX
358ms
AAAA
334ms
TXT
819ms
CAA
330ms
HTTPS
333ms
TLSA
119ms
SOA
373ms
MTA-STS
475ms
DNSSEC
664ms
SRV
355ms
Total
4948ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-01 01:20:33 588ms 2 NS 3 A 0 MX Insecure
2026-10-25 16:08:17 675ms 2 NS 3 A 0 MX Insecure
2026-10-22 01:11:50 556ms 2 NS 3 A 0 MX Insecure
2026-09-25 14:25:21 2427ms 2 NS 3 A 0 MX Insecure
2026-08-27 16:15:14 981ms 2 NS 3 A 0 MX Insecure
2026-08-26 15:13:48 1021ms 2 NS 3 A 0 MX Insecure
2026-08-25 05:11:41 151ms 1 NS 0 A 0 MX Unknown
2026-08-24 04:53:49 2053ms 1 NS 0 A 0 MX Unknown
2026-08-23 02:40:54 2570ms 1 NS 0 A 0 MX Unknown
2026-08-22 02:30:02 1030ms 1 NS 0 A 0 MX Unknown
2026-08-21 02:25:42 shown 4948ms 1 NS 0 A 0 MX Unknown
2026-08-20 01:42:03 4266ms 1 NS 0 A 0 MX Unknown
2026-08-19 00:49:30 2932ms 1 NS 0 A 0 MX Unknown
2026-08-17 17:51:59 747ms 1 NS 0 A 0 MX Unknown
2026-08-16 05:29:54 729ms 1 NS 0 A 0 MX Unknown
2026-08-15 04:19:57 825ms 1 NS 0 A 0 MX Unknown
2026-08-12 19:11:52 2446ms 1 NS 0 A 0 MX Unknown
2026-08-10 21:09:26 788ms 1 NS 0 A 0 MX Unknown
2026-08-09 18:13:10 1559ms 1 NS 0 A 0 MX Unknown
2026-08-08 13:36:12 800ms 1 NS 0 A 0 MX Unknown
2026-08-06 13:51:53 994ms 1 NS 0 A 0 MX Unknown
2026-08-04 05:57:44 2655ms 1 NS 0 A 0 MX Unknown
2026-06-18 05:29:49 1004ms 2 NS 3 A 4 MX Insecure