japanpottery.dk

📜 Historical scan 2026-08-04 20:26:49 · ← Latest scan

🧟 Lame delegation ⬇ Zone File 📜 Timeline & History ⚡ Scan Now

japanpottery.dk is a registered .dk domain whose nameservers (ns1.bigcommerce.com, ns2.bigcommerce.com, ns3.bigcommerce.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 5 January 2019 (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#

3 records 928ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.bigcommerce.com	172.64.52.200 172.64.53.195	— —	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.
ns2.bigcommerce.com	172.64.52.200 172.64.53.195	— —	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.
ns3.bigcommerce.com	172.64.52.200 172.64.53.195	— —	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.

🌍 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

🔗 TLSA / DANE#

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

🔐 DNSSEC#

1107ms

Check	Result
Validation Status	❓ Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates)	✗ Not set
DS Record	✗ Not found
DNSKEY Record	✗ Not found
Flags	resolution failed: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-25 00:56:36

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2019-01-05
Expires	2029-01-31 (829d)

🔗 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#

928ms

1075ms

715ms

AAAA

641ms

TXT

3195ms

CAA

703ms

HTTPS

602ms

TLSA

334ms

SOA

61ms

MTA-STS

736ms

DNSSEC

1107ms

SRV

1073ms

Total

5812ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-23 04:48:59	10986ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 04:41:31	14668ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 04:33:09	10482ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 02:30:06	9264ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 01:19:57	11766ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 22:20:55	8169ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 03:13:11	8206ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 12:49:58	14502ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 11:54:41	8954ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 03:30:46	14933ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 22:55:26	8710ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 14:31:56	8449ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-08 10:37:24	4154ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-06 11:58:04	7998ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-04 20:26:49 shown	5812ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 12:34:59	14488ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 08:13:39	3747ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 07:04:51	6290ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 06:43:33	3715ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 05:38:03	3697ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 04:28:02	6998ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 20:01:42	10193ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 11:44:58	14427ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-19 07:32:44	18324ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-18 00:55:37	14435ms	3 NS 0 A 0 MX	❓ Unknown