nonnareginacph.dk

Historical scan 2026-09-24 03:43:55  ·  ← Latest scan
Zone File Timeline & History Scan Now

nonnareginacph.dk is a .dk domain served by 2 nameservers (ns1.dns-parking.com, ns2.dns-parking.com). It was registered on 16 June 2024 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. The zone is not DNSSEC-signed, has no DMARC policy and is reachable over IPv6. 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   191ms

A Records#

2 records   61ms
IPTTLPTRASNISP / OrgCIDRCountryCity
217.65.156.195 60s — AS47583 — — 🇩🇪 Germany —
217.65.159.4 60s — AS47583 — — 🇩🇪 Germany —

MX Records#

No MX records found

AAAA Records (IPv6)#

2 records   201ms
IPv6 AddressTTLPTRASNISP / OrgCIDRCountryCity
2a02:4780:7f:f758:eb41:dd11:da36:e37 60s — AS47583 — — 🇨🇾 Cyprus —
2a02:4780:80:eae2:1d0d:9512:f268:3bcb 60s — AS47583 — — 🇨🇾 Cyprus —

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 23:06:54

TLSA / DANE#

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

DNSSEC#

142ms
CheckResult
Validation Status Insecure
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsunsigned answer

SOA#

0ms
FieldValue
Serial2026092401
Primary NS (MNAME)ns1.dns-parking.com
Responsible (RNAME)dns@hostinger.com
Refresh10000s
Retry2400s
Expire604800s
Minimum (neg-cache TTL)600s

Registration#

WHOIS fetched 2026-11-05 01:23:26
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2024-06-16
Expires2027-06-15 (210d)

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
191ms
A
61ms
MX
51ms
AAAA
201ms
TXT
393ms
CAA
52ms
HTTPS
51ms
TLSA
85ms
SOA
0ms
MTA-STS
101ms
DNSSEC
142ms
SRV
247ms
Total
837ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-12 23:06:54 799ms 2 NS 2 A 0 MX Insecure
2026-11-05 01:11:07 807ms 2 NS 2 A 0 MX Insecure
2026-10-29 09:26:11 713ms 2 NS 2 A 0 MX Insecure
2026-10-23 10:07:07 655ms 2 NS 2 A 0 MX Insecure
2026-10-16 01:32:53 762ms 2 NS 2 A 0 MX Insecure
2026-10-09 13:34:29 764ms 2 NS 2 A 0 MX Insecure
2026-10-09 12:53:35 1045ms 2 NS 2 A 0 MX Insecure
2026-10-08 10:13:55 1068ms 2 NS 2 A 0 MX Insecure
2026-10-01 05:41:40 855ms 2 NS 2 A 0 MX Insecure
2026-09-24 03:43:55 shown 837ms 2 NS 2 A 0 MX Insecure
2026-09-20 02:57:43 818ms 2 NS 2 A 0 MX Insecure
2026-09-15 23:00:02 1604ms 2 NS 2 A 0 MX Insecure
2026-09-03 17:40:16 696ms 2 NS 2 A 0 MX Insecure
2026-08-29 16:13:35 1347ms 2 NS 2 A 0 MX Insecure
2026-08-27 10:36:42 768ms 2 NS 2 A 0 MX Insecure
2026-08-26 10:32:01 9581ms 2 NS 1 A 0 MX Insecure
2026-08-21 00:32:37 819ms 2 NS 1 A 0 MX Insecure
2026-08-13 17:58:15 2363ms 2 NS 1 A 0 MX Insecure
2026-08-07 01:30:01 1215ms 2 NS 1 A 0 MX Insecure
2026-08-01 18:27:50 1791ms 2 NS 1 A 0 MX Insecure
2026-07-23 02:43:39 2538ms 2 NS 1 A 0 MX Insecure
2026-07-16 11:12:24 11077ms 2 NS 1 A 0 MX Insecure
2026-07-10 03:02:48 715ms 2 NS 1 A 0 MX Insecure
2026-07-03 19:37:47 750ms 2 NS 1 A 0 MX Insecure
2026-06-29 23:53:14 1148ms 2 NS 1 A 0 MX Insecure