lintons.dk

📜 Historical scan 2026-07-19 21:42:12 · ← Latest scan

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

lintons.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 7 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 4030ms

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#

10064ms

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-16 11:06:50

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2008-04-07
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#

4030ms

AAAA

4030ms

TXT

20132ms

CAA

4029ms

HTTPS

4027ms

TLSA

4026ms

SOA

4029ms

MTA-STS

4039ms

DNSSEC

10064ms

SRV

4033ms

Total

61292ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-09 12:41:22	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 03:02:29	61264ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-26 18:55:09	59202ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-20 12:42:48	63729ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 11:03:54	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 10:34:30	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 10:20:51	61372ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 09:31:14	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 05:58:26	63719ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 15:28:24	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 09:12:24	60368ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 21:17:44	55214ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 09:18:57	56426ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 02:09:10	61693ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-08 08:46:45	61315ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 22:44:56	64051ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 13:55:30	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 13:16:19	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 12:30:56	63186ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 11:23:41	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 10:43:04	63440ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 07:45:33	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 21:42:12 shown	61292ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 19:14:07	58220ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 18:35:33	65535ms	2 NS 0 A 0 MX	❓ Unknown