hagmansnordic.dk

Historical scan 2026-07-10 10:11:03  ·  ← Latest scan
Zone File Timeline & History Scan Now

hagmansnordic.dk is a .dk domain served by 2 nameservers (ns1.loopia.se, ns2.loopia.se). It was registered on 28 June 2016 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. The zone is of unknown DNSSEC status, 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   66ms

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 05:55:10
wwwNXDOMAIN
www vs bare domainNeither resolves
hagmansnordic.dk: no address
www.hagmansnordic.dk: no address
WildcardNo
Denial of existenceNSEC3 · 0 iterations · no salt RFC 9276 ✓
CDS / CDNSKEYNone 0 CDS, 0 CDNSKEY

TLSA / DANE#

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

DNSSEC#

154ms
CheckResult
Validation Status Unknown
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Found
Flagsbroken trust chain resolving 'hagmansnordic.dk/DNSKEY/IN': 127.0.0.1#53

SOA#

0ms
FieldValue
Serial1783555200
Primary NS (MNAME)ns1.loopia.se
Responsible (RNAME)registry@loopia.se
Refresh14400s
Retry3600s
Expire604800s
Minimum (neg-cache TTL)86400s

Registration#

WHOIS fetched 2026-11-02 12:19:19
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2016-06-28
Expires2027-06-30 (223d)

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
66ms
A
59ms
MX
52ms
AAAA
62ms
TXT
300ms
CAA
58ms
HTTPS
60ms
TLSA
42ms
SOA
0ms
MTA-STS
96ms
DNSSEC
154ms
SRV
149ms
Total
734ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-12 05:55:10 640ms 2 NS 0 A 0 MX Insecure
2026-11-05 20:27:18 661ms 2 NS 0 A 0 MX Insecure
2026-10-30 20:26:04 703ms 2 NS 0 A 0 MX Insecure
2026-10-22 21:39:43 633ms 2 NS 0 A 0 MX Insecure
2026-10-15 20:36:29 1295ms 2 NS 0 A 0 MX Insecure
2026-10-09 10:24:43 605ms 2 NS 0 A 0 MX Insecure
2026-10-08 11:43:42 869ms 2 NS 0 A 0 MX Insecure
2026-10-01 09:04:40 1872ms 2 NS 0 A 0 MX Insecure
2026-09-26 08:05:02 2401ms 2 NS 0 A 0 MX Insecure
2026-09-24 20:02:19 711ms 2 NS 0 A 0 MX Insecure
2026-09-17 20:18:14 993ms 2 NS 0 A 0 MX Insecure
2026-09-10 18:25:49 783ms 2 NS 0 A 0 MX Insecure
2026-09-06 17:48:22 1919ms 2 NS 0 A 0 MX Insecure
2026-08-27 22:20:19 744ms 2 NS 0 A 0 MX Insecure
2026-08-20 06:44:41 1137ms 2 NS 0 A 0 MX Insecure
2026-08-13 15:50:10 2975ms 2 NS 0 A 0 MX Insecure
2026-08-09 10:34:49 9833ms 2 NS 0 A 0 MX Insecure
2026-08-03 21:50:41 936ms 2 NS 0 A 0 MX Insecure
2026-07-23 14:54:43 9506ms 2 NS 0 A 0 MX Insecure
2026-07-16 08:24:21 876ms 2 NS 0 A 0 MX Insecure
2026-07-10 10:11:03 shown 734ms 2 NS 0 A 0 MX Unknown
2026-07-03 12:30:03 2603ms 2 NS 0 A 0 MX Insecure
2026-06-27 15:07:43 778ms 2 NS 0 A 0 MX Insecure
2026-06-27 01:38:54 1835ms 2 NS 0 A 0 MX Insecure
2026-06-25 02:27:04 887ms 2 NS 0 A 0 MX Insecure