blixenkrone.dk

Historical scan 2026-10-29 06:30:15  ·  ← Latest scan
Zone File Timeline & History Scan Now

blixenkrone.dk is a .dk domain served by 2 nameservers (ns07.sac-it.dk, ns08.sac-it.dk). It was registered on 2 December 1999 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. We saw it become registrar-handled on 5 November 2026, when it moved from direct registration at Punktum to SAC-IT A/S. The zone is not DNSSEC-signed, has no DMARC policy and has no IPv6 address. 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   39ms

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-19 00:12:33
wwwNXDOMAIN
www vs bare domainNeither resolves
blixenkrone.dk: no address
www.blixenkrone.dk: no address
WildcardNo

TLSA / DANE#

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

DNSSEC#

66ms
CheckResult
Validation Status Insecure
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsresolution failed: ncache nxrrset

SOA#

36ms
FieldValue
Serial2026102901
Primary NS (MNAME)ns07.sac-it.dk
Responsible (RNAME)hostmaster@blixenkrone.dk
Refresh10800s
Retry3600s
Expire604800s
Minimum (neg-cache TTL)3600s

Registration#

WHOIS fetched 2026-11-13 07:05:56
FieldValue
RegistrarSAC-IT A/S
Registered1999-12-02
Expires2026-12-31 (41d)

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
39ms
A
30ms
MX
33ms
AAAA
31ms
TXT
173ms
CAA
32ms
HTTPS
26ms
TLSA
39ms
SOA
36ms
MTA-STS
42ms
DNSSEC
66ms
SRV
55ms
Total
355ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-19 00:12:32 552ms 2 NS 0 A 0 MX Insecure
2026-11-13 00:41:09 1090ms 2 NS 0 A 0 MX Insecure
2026-11-05 09:02:12 871ms 2 NS 0 A 0 MX Insecure
2026-10-29 06:30:15 shown 355ms 2 NS 0 A 0 MX Insecure
2026-10-22 06:21:36 924ms 2 NS 0 A 0 MX Insecure
2026-10-15 15:30:10 882ms 2 NS 0 A 0 MX Insecure
2026-10-08 06:56:35 460ms 2 NS 0 A 0 MX Insecure
2026-10-01 05:19:16 604ms 2 NS 0 A 0 MX Insecure
2026-09-30 05:04:08 396ms 2 NS 0 A 0 MX Insecure
2026-09-28 00:29:20 450ms 2 NS 0 A 0 MX Insecure
2026-09-25 00:59:28 429ms 2 NS 0 A 0 MX Insecure
2026-09-18 14:43:25 488ms 2 NS 0 A 0 MX Insecure
2026-09-13 12:22:02 584ms 2 NS 0 A 0 MX Insecure
2026-09-13 11:58:56 504ms 2 NS 0 A 0 MX Insecure
2026-09-06 11:15:04 2355ms 2 NS 0 A 0 MX Insecure
2026-09-03 19:28:34 432ms 2 NS 0 A 0 MX Insecure
2026-08-27 17:34:45 386ms 2 NS 0 A 0 MX Insecure
2026-08-20 12:10:00 8474ms 2 NS 0 A 0 MX Insecure
2026-08-13 10:58:57 599ms 2 NS 0 A 0 MX Insecure
2026-08-09 21:21:39 663ms 2 NS 0 A 0 MX Insecure
2026-08-04 01:13:02 583ms 2 NS 0 A 0 MX Unknown
2026-07-23 03:16:32 680ms 2 NS 0 A 0 MX Insecure
2026-07-16 22:20:21 2404ms 2 NS 0 A 0 MX Insecure
2026-07-11 05:30:13 827ms 2 NS 0 A 0 MX Insecure
2026-07-03 12:47:28 2373ms 2 NS 0 A 0 MX Insecure