zusammenarrangementer.dk

📜 Historical scan 2026-07-08 22:19:32 · ← Latest scan

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

zusammenarrangementer.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 14 September 2023 (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 45ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.one.com	195.206.121.10 2001:67c:28cc::10	ns01.one.com ns01.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns02.one.com	185.10.11.10 2001:67c:3c0::10	ns02.one.com ns02.one.com	AS51468 One.com A/S AS51468 One.com 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#

133ms

Check	Result
Validation Status	⚠️ Bogus — the parent still publishes a DS record, but the delegated nameservers don't answer, so no signed answer can be fetched. The zone isn't serving broken signatures; it isn't serving at all.
AD Flag (resolver validates)	✗ Not set
DS Record	✓ Found
DNSKEY Record	✗ Not found
Flags	resolution failed: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-09 05:18:02

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2023-09-14
Expires	2027-09-13 (328d)

📋 WHOIS#

⏱️ Lookup Timing#

45ms

43ms

AAAA

43ms

TXT

236ms

CAA

54ms

HTTPS

53ms

TLSA

37ms

SOA

33ms

MTA-STS

51ms

DNSSEC

133ms

SRV

177ms

Total

8869ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 04:24:50	1248ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-09-11 12:58:16	1148ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-09-02 16:18:16	49339ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 14:33:14	10138ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-24 02:32:42	2947ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-22 18:18:08	2028ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-21 18:11:48	1909ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-20 18:11:24	17418ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-19 17:24:58	5091ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-18 17:22:53	3645ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-17 07:25:17	1422ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-15 17:21:58	1131ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-14 14:38:56	3437ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-13 05:18:19	2682ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-12 04:58:31	10110ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-11 04:25:34	26409ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 10:43:42	17178ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 03:00:15	16648ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-07 00:06:59	27291ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 08:40:51	12088ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-29 03:53:17	27244ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 06:37:45	14152ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-26 06:08:23	939ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-25 05:56:33	10033ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-24 04:49:42	31157ms	2 NS 0 A 0 MX	❓ Unknown