printorama.dk

Historical scan 2026-08-06 02:49:32  ·  ← Latest scan
Lame delegation Zone File Timeline & History Scan Now

printorama.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 24 April 2025 (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#

2 records   161ms

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-10-25 21:32:38
www CNAMEshops.myshopify.com (all on myshopify.com)
www vs bare domainSame network
printorama.dk: 23.227.38.65 (AS13335)
www.printorama.dk: 23.227.38.74 2620:127:f00f:e:: (AS13335)
WildcardNo

TLSA / DANE#

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

DNSSEC#

249ms
CheckResult
Validation Status Bogus — the parent still publishes a DS record, but the delegated nameservers don't answer, so no signed answer can be fetched. The zone isn't serving broken signatures; it isn't serving at all.
AD Flag (resolver validates) Not set
DS Record Found
DNSKEY Record Not found
Flagsresolution failed: failure

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-10-25 13:56:41
FieldValue
RegistrarONE.COM A/S
Registered2025-04-24
Expires2027-04-23 (157d)

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
161ms
A
130ms
MX
138ms
AAAA
186ms
TXT
601ms
CAA
191ms
HTTPS
200ms
TLSA
117ms
SOA
52ms
MTA-STS
154ms
DNSSEC
249ms
SRV
205ms
Total
1402ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-10-25 21:32:38 928ms 2 NS 1 A 3 MX Insecure
2026-10-02 13:03:32 744ms 2 NS 1 A 3 MX Insecure
2026-09-25 00:35:49 1110ms 2 NS 1 A 3 MX Insecure
2026-09-23 23:52:37 974ms 2 NS 1 A 1 MX Insecure
2026-08-26 19:43:57 409ms 2 NS 1 A 1 MX Insecure
2026-08-25 14:44:47 47215ms 2 NS 0 A 0 MX Unknown
2026-08-23 10:04:43 9049ms 2 NS 0 A 0 MX Bogus
2026-08-22 08:56:06 2959ms 2 NS 0 A 0 MX Bogus
2026-08-21 08:50:20 5028ms 2 NS 0 A 0 MX Bogus
2026-08-20 07:58:44 5572ms 2 NS 0 A 0 MX Bogus
2026-08-19 05:46:11 1987ms 2 NS 0 A 0 MX Bogus
2026-08-17 08:59:23 27256ms 2 NS 0 A 0 MX Unknown
2026-08-15 11:25:42 3027ms 2 NS 0 A 0 MX Bogus
2026-08-13 22:09:35 5213ms 2 NS 0 A 0 MX Bogus
2026-08-12 04:50:32 1109ms 2 NS 0 A 0 MX Bogus
2026-08-11 03:01:24 3871ms 2 NS 0 A 0 MX Bogus
2026-08-06 02:49:32 shown 1402ms 2 NS 0 A 0 MX Bogus
2026-07-30 01:40:27 12267ms 2 NS 0 A 0 MX Unknown
2026-07-27 16:18:35 992ms 2 NS 0 A 0 MX Bogus
2026-07-26 15:28:27 10105ms 2 NS 0 A 0 MX Bogus
2026-07-25 14:23:07 10052ms 2 NS 0 A 0 MX Bogus
2026-07-24 14:08:53 16889ms 2 NS 0 A 0 MX Bogus
2026-07-23 13:17:33 815ms 2 NS 0 A 0 MX Bogus
2026-07-22 11:52:18 8717ms 2 NS 0 A 0 MX Bogus
2026-07-21 07:21:19 10091ms 2 NS 0 A 0 MX Bogus