topti-auto.dk

📜 Historical scan 2026-07-24 13:55:10 · ← Latest scan

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

topti-auto.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 2 June 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#

10062ms

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 18:51:09

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2008-06-02
Expires	2027-06-30 (249d)

🔗 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

AAAA

4028ms

TXT

20121ms

CAA

4028ms

HTTPS

4025ms

TLSA

4027ms

SOA

4028ms

MTA-STS

4037ms

DNSSEC

10062ms

SRV

4032ms

Total

63178ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-23 18:33:46	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 09:38:00	59303ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 09:23:18	60175ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 09:17:05	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 06:57:36	57605ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 21:31:55	57232ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 10:29:43	57910ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 10:12:41	65335ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 21:18:44	60641ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 10:54:32	54356ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 17:23:10	55259ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 08:50:00	59491ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 20:47:39	64012ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 02:26:07	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 08:26:18	61250ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 15:24:32	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 14:56:43	63227ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 14:31:36	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 13:55:10 shown	63178ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 13:40:39	61344ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 13:11:05	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 11:28:11	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 11:43:57	57487ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 08:50:06	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 07:30:24	65535ms	2 NS 0 A 0 MX	❓ Unknown