1-2-3markiser.dk

📜 Historical scan 2026-07-29 10:20:38 · ← Latest scan

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

1-2-3markiser.dk is a registered .dk domain whose nameservers (ns.dandomain.dk, ns2.dandomain.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 6 April 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 73ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.dandomain.dk	185.25.141.3 2a02:2339:4006:109::dd	ns.dandomain.dk ns.dandomain.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.dandomain.dk	2a02:2339:1:108::dd:dd 91.197.248.66	ns2.dandomain.dk ns2.dandomain.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark 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#

102ms

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-15 13:52:32

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

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

73ms

72ms

73ms

AAAA

71ms

TXT

315ms

CAA

73ms

HTTPS

72ms

TLSA

61ms

SOA

25ms

MTA-STS

79ms

DNSSEC

102ms

SRV

74ms

Total

1104ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-08 20:18:57	767ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-07 16:33:38	801ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 10:28:34	1055ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 21:04:29	924ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 06:58:36	4133ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 00:49:31	9942ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 00:43:48	9541ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 00:25:32	1703ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 23:00:22	5054ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 22:26:08	2915ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 09:40:23	3629ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 02:32:32	4348ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 22:30:21	2914ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 05:50:26	2920ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 05:34:47	4366ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 16:30:48	10095ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 13:09:45	9904ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 17:48:40	1129ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 21:56:46	2517ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 10:20:38 shown	1104ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 04:14:00	9074ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 03:37:41	2755ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 03:18:22	9970ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 02:51:35	1000ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 02:18:44	9964ms	2 NS 0 A 0 MX	❓ Unknown