livingenmore.dk

Historical scan 2026-06-17 17:32:49  ·  ← Latest scan
Zone File Timeline & History Scan Now

livingenmore.dk is a .dk domain served by 2 nameservers (ns1.dns-parking.com, ns2.dns-parking.com). It was registered on 7 January 2026 (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   153ms

A Records#

1 records   159ms
IPTTLPTRASNISP / OrgCIDRCountryCity
23.227.38.65 — myshopify.com AS13335 — — — —

MX Records#

No MX records found

AAAA Records (IPv6)#

1 records   157ms
IPv6 AddressTTLPTRASNISP / OrgCIDRCountryCity
2620:127:f00f:e:: — — AS13335 — — — —

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 10:00:55
www CNAMEshops.myshopify.com (all on myshopify.com)
www vs bare domainSame network
WildcardNo

TLSA / DANE#

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

DNSSEC#

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

SOA#

245ms
FieldValue
Serial2026061101
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 07:05:29
FieldValue
RegistrarRealtime Register B.V.
Registered2026-01-07
Expires2027-01-06 (49d)

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
153ms
A
159ms
MX
296ms
AAAA
157ms
TXT
402ms
CAA
269ms
HTTPS
265ms
TLSA
123ms
SOA
245ms
MTA-STS
147ms
DNSSEC
279ms
SRV
0ms
Total
910ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-12 10:00:54 2137ms 2 NS 1 A 0 MX Insecure
2026-11-05 06:30:54 1121ms 2 NS 1 A 0 MX Insecure
2026-10-29 03:30:35 731ms 2 NS 1 A 0 MX Insecure
2026-10-25 14:14:41 641ms 2 NS 1 A 0 MX Insecure
2026-10-23 21:37:04 1192ms 2 NS 1 A 0 MX Insecure
2026-10-22 10:31:46 661ms 2 NS 1 A 0 MX Insecure
2026-10-15 22:47:50 1612ms 2 NS 1 A 0 MX Insecure
2026-10-08 09:03:31 1000ms 2 NS 1 A 0 MX Insecure
2026-10-01 03:39:10 926ms 2 NS 1 A 0 MX Insecure
2026-09-25 02:15:15 1072ms 2 NS 1 A 0 MX Insecure
2026-09-18 12:13:29 785ms 2 NS 1 A 0 MX Insecure
2026-09-11 10:07:04 3502ms 2 NS 1 A 0 MX Insecure
2026-09-06 10:01:04 932ms 2 NS 1 A 0 MX Insecure
2026-08-27 02:38:48 1069ms 2 NS 1 A 0 MX Insecure
2026-08-21 00:58:33 2682ms 2 NS 1 A 0 MX Insecure
2026-08-13 02:04:54 16709ms 2 NS 1 A 0 MX Insecure
2026-08-07 15:51:44 1076ms 2 NS 1 A 0 MX Insecure
2026-07-31 13:38:02 982ms 2 NS 1 A 0 MX Insecure
2026-07-23 02:37:37 9514ms 2 NS 1 A 0 MX Insecure
2026-07-17 08:23:34 874ms 2 NS 1 A 0 MX Insecure
2026-07-11 15:27:10 1062ms 2 NS 1 A 0 MX Insecure
2026-07-03 13:32:14 2472ms 2 NS 1 A 0 MX Insecure
2026-06-25 15:44:29 694ms 2 NS 1 A 0 MX Insecure
2026-06-21 04:01:15 929ms 2 NS 1 A 0 MX Insecure
2026-06-17 17:32:49 shown 910ms 2 NS 1 A 0 MX Insecure