bookingpartnerinc.dk

📜 Historical scan 2026-08-23 23:52:49 · ← Latest scan

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

bookingpartnerinc.dk is a registered .dk domain whose nameservers (ns1.syrahost.com, ns2.syrahost.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 27 February 2021 (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 150ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.syrahost.com	172.64.52.175 2606:4700:52::ac40:34af	— —	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.
ns2.syrahost.com	172.64.53.58 2606:4700:5a::ac40:353a	— —	AS13335 Cloudflare, Inc. AS13335 Cloudflare, 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#

319ms

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-18 20:00:47

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2021-02-27
Expires	2027-02-28 (130d)

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

150ms

199ms

195ms

AAAA

186ms

TXT

907ms

CAA

154ms

HTTPS

197ms

TLSA

330ms

SOA

70ms

MTA-STS

724ms

DNSSEC

319ms

SRV

2394ms

Total

4261ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-26 03:05:46	10025ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 23:52:49 shown	4261ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 18:42:41	8824ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 18:35:14	13774ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 18:28:13	13067ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 12:49:13	9218ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 12:44:43	13625ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 04:23:16	13785ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 00:55:13	12893ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 08:10:04	12631ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 00:49:09	12873ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 19:49:58	14587ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 13:41:08	8930ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 09:18:37	5835ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 11:54:20	7398ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 00:43:54	12944ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 03:37:57	8617ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 02:20:38	10444ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 02:10:51	8888ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 01:46:15	17243ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 01:21:47	9901ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 00:49:03	8529ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 00:04:40	7804ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 12:18:28	21635ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 05:27:15	8562ms	2 NS 0 A 0 MX	❓ Unknown