jettingscrews.dk

📜 Historical scan 2026-07-28 02:04:24 · ← Latest scan

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

jettingscrews.dk is a registered .dk domain whose nameservers (ns1.fsdatans.net, ns2.fsdatans.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 23 July 2019 (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 155ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.fsdatans.net	162.159.24.16 2400:cb00:2049:1::a29f:1810	ns1.fsdatans.net —	AS13335 Cloudflare, Inc. AS13335 Cloudflare, Inc.
ns2.fsdatans.net	162.159.25.37 2400:cb00:2049:1::a29f:1925	ns2.fsdatans.net —	AS13335 Cloudflare, Inc. AS13335 Cloudflare, 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#

191ms

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: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-11 22:45:29

Field	Value
Registrar	Name SRS AB
Registered	2019-07-23
Expires	2027-07-31 (285d)

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

155ms

163ms

149ms

AAAA

176ms

TXT

812ms

CAA

151ms

HTTPS

155ms

TLSA

158ms

SOA

24ms

MTA-STS

174ms

DNSSEC

191ms

SRV

205ms

Total

1963ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-24 22:40:19	10897ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-19 06:59:07	10780ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 07:27:46	4417ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 07:08:41	5977ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 07:02:06	1464ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 06:28:11	1870ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 06:11:52	3543ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 23:54:00	4234ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 20:29:32	10588ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 19:39:43	4633ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 03:35:49	5090ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 16:15:32	9187ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 12:54:57	5135ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 16:09:00	2368ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 02:04:24 shown	1963ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 01:48:13	25277ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 00:59:49	1104ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 00:27:45	998ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 19:32:45	1879ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 17:35:53	10355ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 13:05:53	10429ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 10:29:13	941ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 09:42:08	8886ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 04:26:29	839ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-15 22:08:49	886ms	2 NS 0 A 0 MX	❓ Unknown