bari.dk

📜 Historical scan 2026-07-23 00:40:17 · ← Latest scan

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

bari.dk is a registered .dk domain whose nameservers (ns1.nameservices.us, ns2.nameservices.us) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 8 June 2001 (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 16046ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.nameservices.us	—	—	—
ns2.nameservices.us	—	—	—

🌍 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-02 22:31:43

www	Address record (no CNAME)
Wildcard	Yes: any name under the zone resolves

🔗 TLSA / DANE#

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

🔐 DNSSEC#

16073ms

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: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-14 09:05:49

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2001-06-08
Expires	2027-06-30 (252d)

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

16046ms

16034ms

16041ms

AAAA

16041ms

TXT

65535ms

CAA

16065ms

HTTPS

16050ms

TLSA

16031ms

SOA

16039ms

MTA-STS

16068ms

DNSSEC

16073ms

SRV

16068ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-05 22:43:29	1247ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-02 22:31:43	2634ms	2 NS 1 A 1 MX	🔓 Insecure
2026-10-01 22:31:02	2693ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-30 22:22:36	3441ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-28 22:07:53	3169ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-27 21:48:29	4326ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-26 21:38:25	3275ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-25 21:18:54	3196ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-24 21:10:37	3176ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-23 20:24:25	3265ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-22 12:42:19	3302ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-18 21:15:32	3291ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-12 09:46:52	3216ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-08 06:50:21	10083ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-08 01:16:43	3235ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-03 16:51:25	10285ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-03 13:07:35	3181ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-01 11:32:01	3297ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-31 05:47:53	3848ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-29 18:34:48	3276ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-28 16:36:00	3182ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-27 13:16:33	3136ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-26 12:09:15	3060ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-24 01:05:45	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 19:51:01	65535ms	2 NS 0 A 0 MX	❓ Unknown