sibu.dk

📜 Historical scan 2026-07-20 22:06:00 · ← Latest scan

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

sibu.dk is a registered .dk domain whose nameservers (ns1.greengeeks.net, ns2.greengeeks.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 29 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 80ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.greengeeks.net	75.2.69.7	aba07164e9478179d.awsglobalaccelerator.com	AS16509 Amazon.com, Inc.
ns2.greengeeks.net	99.83.188.187	aba07164e9478179d.awsglobalaccelerator.com	AS16509 Amazon.com, 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#

133ms

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-13 04:05:03

Field	Value
Registrar	Name SRS AB
Registered	2025-04-29
Expires	2027-04-28 (184d)

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

80ms

65ms

67ms

AAAA

73ms

TXT

266ms

CAA

72ms

HTTPS

72ms

TLSA

83ms

SOA

22ms

MTA-STS

86ms

DNSSEC

133ms

SRV

748ms

Total

1287ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-25 21:02:03	3119ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-21 19:55:54	4454ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-27 18:39:32	3244ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-04 04:47:24	11200ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 03:08:23	4778ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 22:12:58	4230ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 22:00:15	11363ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 21:56:42	3317ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 21:19:29	3361ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 21:13:17	8553ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 19:42:11	6582ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 16:43:48	2535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 14:26:42	5211ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 05:38:35	3200ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 11:56:39	14765ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 09:12:16	6595ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 15:10:20	6317ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 21:19:26	3341ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 09:36:43	9017ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 09:16:30	1462ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 09:07:42	9571ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 07:32:34	3363ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 06:46:36	1114ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 05:59:33	16736ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 22:06:00 shown	1287ms	2 NS 0 A 0 MX	❓ Unknown