kuroe-sushi.dk

📜 Historical scan 2026-08-23 04:08:56 · ← Latest scan

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

kuroe-sushi.dk is a registered .dk domain whose nameservers (ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org and 1 more) do not answer for it, so it is currently a lame delegation and does not resolve. It 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#

4 records 811ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1-09.azure-dns.com	13.107.236.9 2603:1061:0:700::9	ns1-09.azure-dns.com ns1-09.azure-dns.com	AS8075 Microsoft Corporation AS8075 Microsoft Corporation
ns2-09.azure-dns.net	150.171.21.9 2620:1ec:8ec:700::9	ns2-09.azure-dns.net ns2-09.azure-dns.net	AS8075 Microsoft Corporation AS8075 Microsoft Corporation
ns3-09.azure-dns.org	204.14.183.9 2a01:111:4000:700::9	ns3-09.azure-dns.org ns3-09.azure-dns.org	AS8075 Microsoft Corporation AS8075 Microsoft Corporation
ns4-09.azure-dns.info	208.84.5.9 2620:1ec:bda:700::9	ns4-09.azure-dns.info ns4-09.azure-dns.info	AS8075 Microsoft Corporation AS8075 Microsoft Corporation

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

883ms

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#

✗ No registration data yet — queued for a WHOIS lookup

📋 WHOIS#

⏱️ Lookup Timing#

811ms

683ms

590ms

AAAA

588ms

TXT

2378ms

CAA

780ms

HTTPS

633ms

TLSA

432ms

SOA

335ms

MTA-STS

861ms

DNSSEC

883ms

SRV

680ms

Total

6861ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-04 01:53:03	2470ms	4 NS 0 A 0 MX	❓ Unknown
2026-09-30 22:01:13	2569ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-27 05:08:43	3858ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-23 04:08:56 shown	6861ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-22 03:45:05	2402ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-21 03:42:37	2191ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-20 03:36:21	18641ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-19 00:13:19	5251ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-17 17:03:22	4831ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-16 11:02:19	4133ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-14 08:05:33	5916ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-13 07:44:30	4095ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-12 06:22:28	11153ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-11 04:11:21	2972ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-10 03:28:50	6343ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-09 01:47:40	2995ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-04 21:47:41	4149ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-29 14:19:57	10958ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:48:34	1869ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-26 23:17:48	1741ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-25 22:54:07	1675ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-24 22:26:10	10088ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-23 21:52:38	2201ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-22 20:31:11	9044ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-21 18:44:43	10946ms	4 NS 0 A 0 MX	❓ Unknown