taskschedule.dk

📜 Historical scan 2026-07-16 18:19:52 · ← Latest scan

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

taskschedule.dk is a registered .dk domain whose nameservers (dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net and 1 more) do not answer for it, so it is currently a lame delegation and does not resolve. It 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#

4 records 164ms

Nameserver	IP addresses	PTR	ASN / ISP
dns1.p06.nsone.net	198.51.44.6 2620:4d:4000:6259:7:6:0:1	dns1.p06.nsone.net —	AS62597 NSONE Inc AS62597 NSONE Inc
dns2.p06.nsone.net	198.51.45.6 2a00:edc0:6259:7:6::2	dns2.p06.nsone.net dns2.p06.nsone.net	AS62597 NSONE Inc AS62597 NSONE Inc
dns3.p06.nsone.net	198.51.44.70 2620:4d:4000:6259:7:6:0:3	dns3.p06.nsone.net —	AS62597 NSONE Inc AS62597 NSONE Inc
dns4.p06.nsone.net	198.51.45.70 2a00:edc0:6259:7:6::4	dns4.p06.nsone.net dns4.p06.nsone.net	AS62597 NSONE Inc AS62597 NSONE 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#

240ms

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#

✗ No registration data yet — queued for a WHOIS lookup

📋 WHOIS#

⏱️ Lookup Timing#

164ms

159ms

162ms

AAAA

176ms

TXT

809ms

CAA

162ms

HTTPS

163ms

TLSA

220ms

SOA

34ms

MTA-STS

169ms

DNSSEC

240ms

SRV

793ms

Total

10698ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 19:31:11	6186ms	4 NS 0 A 0 MX	❓ Unknown
2026-09-15 13:09:47	12919ms	4 NS 0 A 0 MX	❓ Unknown
2026-09-08 20:49:16	6097ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-23 13:39:09	6295ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-22 12:01:47	3406ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-21 11:39:00	14250ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-20 10:51:20	2935ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-19 10:14:54	8685ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-18 10:12:16	7825ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-16 19:35:13	6786ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-15 02:29:45	8435ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-13 02:32:11	2640ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-10 22:44:53	7877ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-09 21:58:00	12780ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-07 12:54:36	9785ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-04 14:31:41	6092ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-28 10:08:10	13617ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-27 06:56:44	4263ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-26 06:30:48	7208ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-25 06:15:27	10303ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-24 04:41:21	10315ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-23 04:13:12	4933ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-22 00:29:40	6416ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-20 15:39:16	2408ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-19 00:41:21	3732ms	4 NS 0 A 0 MX	❓ Unknown