friismaerker.dk

📜 Historical scan 2026-08-20 06:27:22 · ← Latest scan

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

friismaerker.dk is a registered .dk domain whose nameservers (ns2.123hjemmeside.dk, ns3.123hjemmeside.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 1 March 2008 (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 4110ms

Nameserver	IP addresses	PTR	ASN / ISP
ns2.123hjemmeside.dk	52.200.246.146	ec2-52-200-246-146.compute-1.amazonaws.com	AS14618 Amazon.com, Inc.
ns3.123hjemmeside.dk	52.51.2.215	ec2-52-51-2-215.eu-west-1.compute.amazonaws.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#

10129ms

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: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-22 02:15:06

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2008-03-01
Expires	2027-03-31 (159d)

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

4110ms

4078ms

2066ms

AAAA

4089ms

TXT

56222ms

CAA

2081ms

HTTPS

4108ms

TLSA

2047ms

SOA

51ms

MTA-STS

4115ms

DNSSEC

10129ms

SRV

16076ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-08 07:20:25	62224ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-01 05:10:11	59188ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-28 00:03:50	61125ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 15:22:28	59341ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 11:50:01	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 07:42:05	55348ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 07:22:21	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 07:09:23	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 06:27:22 shown	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 06:11:32	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 05:52:15	56418ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 03:54:42	61756ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 19:55:37	57314ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 08:46:55	61285ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 03:19:33	61380ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 14:21:36	59082ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 10:49:16	64525ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 11:33:50	58402ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 03:18:56	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 11:50:30	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 22:27:07	53179ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 02:54:25	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 02:22:08	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 01:53:18	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 01:20:56	65535ms	2 NS 0 A 0 MX	❓ Unknown