trine-peter.dk

📜 Historical scan 2026-07-12 16:31:01 · ← Latest scan

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

trine-peter.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 4 April 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 4027ms

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#

10058ms

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-23 23:46:36

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2008-04-04
Expires	2027-04-30 (188d)

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

4027ms

4028ms

4031ms

AAAA

4031ms

TXT

20134ms

CAA

4031ms

HTTPS

4035ms

TLSA

4028ms

SOA

4030ms

MTA-STS

4037ms

DNSSEC

10058ms

SRV

4039ms

Total

63287ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 17:36:10	59056ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-26 04:50:50	61188ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 16:42:25	63647ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 03:54:36	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 00:54:46	64382ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 00:41:37	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 00:26:18	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 23:44:59	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 22:42:24	65332ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 12:03:25	63463ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 04:18:32	61888ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 15:19:15	60786ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 13:52:04	53370ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 11:04:37	60605ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 20:43:37	63253ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 20:00:23	63478ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 11:01:00	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 21:09:53	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 20:31:23	61254ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 19:35:46	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 18:58:47	57305ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 17:21:29	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 15:33:53	61187ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 13:54:39	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 06:51:53	65535ms	2 NS 0 A 0 MX	❓ Unknown