nibonya-sushi.dk

Records from scan: 2026-09-28 07:20:09 · 10747ms total · last checked 2026-10-24 12:37 (unchanged)

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

nibonya-sushi.dk is a registered .dk domain whose nameservers (ns1-02.azure-dns.com, ns3-02.azure-dns.org, ns4-02.azure-dns.info) 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 our latest scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.

🖥️ Nameservers#

3 records 188ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1-02.azure-dns.com	13.107.236.2 2603:1061:0:700::2	ns1-02.azure-dns.com ns1-02.azure-dns.com	AS8075 Microsoft Corporation AS8075 Microsoft Corporation
ns3-02.azure-dns.org	204.14.183.2 2a01:111:4000:700::2	ns3-02.azure-dns.org ns3-02.azure-dns.org	AS8075 Microsoft Corporation AS8075 Microsoft Corporation
ns4-02.azure-dns.info	208.84.5.2 2620:1ec:bda:700::2	ns4-02.azure-dns.info ns4-02.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#

9249ms

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#

188ms

195ms

187ms

AAAA

191ms

TXT

919ms

CAA

197ms

HTTPS

239ms

TLSA

185ms

SOA

195ms

MTA-STS

313ms

DNSSEC

9249ms

SRV

204ms

Total

10747ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-28 07:20:09 shown	10747ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-21 18:46:52	12608ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 19:15:09	10859ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 17:22:32	3635ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 17:16:16	2429ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 17:01:15	3834ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 13:02:23	10960ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 12:58:47	4118ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 14:26:53	3923ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 19:42:28	1307ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 18:55:34	6458ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 06:26:38	9150ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 21:27:45	1779ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 11:58:28	9399ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-06 14:21:33	5709ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 19:36:26	2298ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 20:16:17	1296ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 19:23:56	2298ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 18:50:45	3400ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 18:32:11	1272ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 16:38:34	10608ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 16:17:38	1266ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 11:46:41	9734ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 11:16:01	1231ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-19 00:48:49	1407ms	3 NS 0 A 0 MX	❓ Unknown