julesiden.dk

Historical scan 2026-06-22 05:49:28  ·  ← Latest scan
Zone File Timeline & History Scan Now

julesiden.dk is a .dk domain with no delegation in this scan. It was registered on 9 February 2004 (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-12 20:03:50
www CNAMEjulesiden.dk (all on julesiden.dk)
www vs bare domainSame network
julesiden.dk: 217.116.232.212 (AS47292)
www.julesiden.dk: 217.116.232.212 (AS47292)
WildcardYes: any name under the zone resolves

TLSA / DANE#

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

DNSSEC#

508ms
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-05 03:58:44
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2004-02-09
Expires2027-02-28 (102d)

Same registrant#

1 domain

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).

DomainRegistrar
oelsted.dkPunktum dk A/S (direct)
📋 WHOIS#

Lookup Timing#

NS
208ms
A
202ms
MX
191ms
AAAA
221ms
TXT
541ms
CAA
178ms
HTTPS
243ms
TLSA
18ms
SOA
172ms
MTA-STS
195ms
DNSSEC
508ms
SRV
224ms
Total
1164ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-12 20:03:50 1754ms 5 NS 1 A 3 MX Insecure
2026-11-05 03:45:02 1447ms 5 NS 1 A 3 MX Insecure
2026-11-03 00:41:25 1726ms 5 NS 1 A 3 MX Insecure
2026-10-29 03:41:24 1340ms 5 NS 1 A 3 MX Insecure
2026-10-24 14:02:01 1732ms 5 NS 1 A 3 MX Insecure
2026-10-15 15:20:17 1066ms 5 NS 1 A 3 MX Insecure
2026-10-08 05:41:54 2644ms 5 NS 1 A 3 MX Insecure
2026-10-04 01:04:20 618ms 5 NS 1 A 3 MX Insecure
2026-10-01 08:17:44 2762ms 5 NS 1 A 3 MX Insecure
2026-09-24 05:54:21 1051ms 5 NS 1 A 3 MX Insecure
2026-09-21 17:39:20 1215ms 5 NS 1 A 3 MX Insecure
2026-09-11 15:12:10 1075ms 5 NS 1 A 3 MX Insecure
2026-09-07 21:38:04 1033ms 5 NS 1 A 3 MX Insecure
2026-08-27 15:16:28 963ms 5 NS 1 A 3 MX Insecure
2026-08-20 15:36:15 8681ms 5 NS 1 A 3 MX Insecure
2026-08-14 10:47:56 2901ms 5 NS 1 A 3 MX Insecure
2026-08-06 03:10:44 1056ms 5 NS 1 A 3 MX Insecure
2026-08-01 16:01:31 1121ms 5 NS 1 A 3 MX Insecure
2026-07-24 20:38:13 25306ms 5 NS 1 A 3 MX Insecure
2026-07-23 20:26:20 1312ms 5 NS 1 A 3 MX Insecure
2026-07-17 00:59:57 953ms 5 NS 1 A 3 MX Insecure
2026-07-12 15:59:49 9738ms 5 NS 1 A 3 MX Insecure
2026-07-03 11:22:59 1846ms 5 NS 1 A 3 MX Insecure
2026-06-26 15:28:06 1664ms 5 NS 1 A 3 MX Insecure
2026-06-23 18:27:05 3210ms 5 NS 1 A 3 MX Insecure