baobabgroup.dk

📜 Historical scan 2026-07-27 23:43:22 · ← Latest scan

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

baobabgroup.dk is a registered .dk domain whose nameservers (dns1.pro.dk, dns2.pro.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 2 August 2016 (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 42ms

Nameserver	IP addresses	PTR	ASN / ISP
dns1.pro.dk	37.140.219.20	—	AS31027 GlobalConnect A/S
dns2.pro.dk	37.140.219.21	—	AS31027 GlobalConnect A/S

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

120ms

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-19 22:04:11

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2016-08-02
Expires	2027-08-31 (315d)

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

42ms

31ms

47ms

AAAA

43ms

TXT

378ms

CAA

48ms

HTTPS

41ms

TLSA

26ms

SOA

32ms

MTA-STS

65ms

DNSSEC

120ms

SRV

185ms

Total

3350ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-26 23:09:42	804ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-08 11:45:29	2855ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-07 14:51:22	763ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-28 03:51:12	994ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 17:03:01	10947ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 19:41:55	1944ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 15:42:25	2779ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 15:24:12	6847ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 15:16:37	922ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 12:41:20	3593ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 12:32:48	4659ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 19:26:33	2533ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 16:27:18	4078ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 15:50:54	3200ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 00:50:18	3124ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 03:43:58	2552ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 16:34:35	3706ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 00:44:48	9780ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:43:22 shown	3350ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 23:10:45	847ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 21:40:06	12525ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 21:11:49	954ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 19:31:02	1307ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 19:18:05	985ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 03:45:19	1093ms	2 NS 0 A 0 MX	❓ Unknown