sightspeed.dk

📜 Historical scan 2026-07-27 04:28:29 · ← Latest scan

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

sightspeed.dk is a registered .dk domain whose nameservers (ns-1.logitech.com, ns-2.logitech.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 10 July 2003 (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
ns-1.logitech.com	184.72.110.167 2600:1f18:25aa:6a02:f61d:e548:a147:51c6	ns-1.logitech.com —	AS14618 Amazon.com, Inc. AS14618 Amazon.com, Inc.
ns-2.logitech.com	2600:1f1c:6df:c01:361a:9a56:9d82:93d4 54.219.144.49	— ns-2.logitech.com	AS16509 Amazon.com, Inc. 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#

10063ms

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-11 14:48:07

Field	Value
Registrar	MarkMonitor Inc.
Registered	2003-07-10
Expires	2027-07-31 (287d)

🔗 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

2026ms

AAAA

4025ms

TXT

10118ms

CAA

2024ms

HTTPS

2025ms

TLSA

2026ms

SOA

22ms

MTA-STS

2034ms

DNSSEC

10063ms

SRV

2028ms

Total

22364ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-08 14:39:13	30953ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 07:14:40	8159ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 07:04:18	31944ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 06:39:35	7615ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 04:53:40	37873ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 01:28:17	35180ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 18:19:14	6233ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 23:22:37	31244ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 17:36:46	27886ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 02:11:21	35313ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 08:52:01	35630ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 01:14:07	32577ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 18:49:59	11968ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 06:18:07	6559ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 19:01:18	23931ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 05:24:44	36582ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 04:28:29 shown	22364ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 04:25:48	20808ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 04:02:33	22309ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 03:30:07	9272ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 02:44:23	16146ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 09:05:52	8789ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 04:23:16	11673ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 23:06:04	15924ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 20:21:01	35177ms	2 NS 0 A 0 MX	❓ Unknown