tosk.dk

📜 Historical scan 2026-08-13 02:20:05 · ← Latest scan

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

tosk.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 2 October 2012 (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 4177ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.one.com	195.206.121.10 2001:67c:28cc::10	ns01.one.com ns01.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns02.one.com	185.10.11.10 2001:67c:3c0::10	ns02.one.com ns02.one.com	AS51468 One.com A/S AS51468 One.com A/S

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

10504ms

Check	Result
Validation Status	❓ Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates)	✗ Not set
DS Record	✓ Found
DNSKEY Record	✗ Not found
Flags	resolution failed: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-12 21:32:13

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2012-10-02
Expires	2026-10-31 (3d)

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

4177ms

4179ms

AAAA

4163ms

TXT

14605ms

CAA

4168ms

HTTPS

4166ms

TLSA

118ms

SOA

4167ms

MTA-STS

4226ms

DNSSEC

10504ms

SRV

4206ms

Total

27405ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-22 16:54:59	1836ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-10-02 13:22:16	3388ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-09-30 12:59:18	1381ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-24 10:54:43	1503ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-23 05:21:04	4011ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-22 04:58:14	4511ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-21 04:39:51	1482ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-20 00:33:22	1308ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-18 22:46:51	5601ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-17 13:57:54	38107ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-15 19:57:47	1543ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-14 10:27:35	2951ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-13 02:20:05 shown	27405ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 01:13:27	53489ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 11:54:51	2410ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-08 11:49:12	1492ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-07 10:08:28	9032ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-03 22:07:56	944ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-28 17:26:37	51737ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 09:48:22	958ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-26 09:24:52	922ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-25 09:08:35	29160ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 08:42:02	23416ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 08:29:24	1072ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-22 04:45:46	880ms	2 NS 0 A 0 MX	⚠️ Bogus