fashioo.dk

📜 Historical scan 2026-08-01 21:37:48 · ← Latest scan

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

fashioo.dk is a registered .dk domain whose nameservers (dns106.ovh.net, ns106.ovh.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 19 October 2013 (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 499ms

Nameserver	IP addresses	PTR	ASN / ISP
dns106.ovh.net	2001:41d0:d01::2 5.196.41.1	dns106.ovh.net dns106.ovh.net	AS16276 OVH SAS AS16276 OVH SAS
ns106.ovh.net	2001:41d0:b00:fa00::2 5.135.65.21	ns106.ovh.net ns106.ovh.net	AS16276 OVH SAS AS16276 OVH SAS

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

570ms

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-17 07:46:31

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2013-10-19
Expires	2026-10-31 (11d)

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

499ms

8218ms

500ms

AAAA

569ms

TXT

1541ms

CAA

496ms

HTTPS

497ms

TLSA

123ms

SOA

30ms

MTA-STS

157ms

DNSSEC

570ms

SRV

819ms

Total

10101ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-22 01:49:20	11670ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 15:15:15	3710ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 04:17:49	5446ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 01:27:01	3237ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 00:58:21	3606ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 00:49:06	7096ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 23:46:50	3854ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 21:58:15	2874ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 16:58:26	11589ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 06:59:36	3580ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 23:35:16	2600ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 18:54:33	11823ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 13:15:23	6809ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 10:18:49	7128ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 08:41:58	8563ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 21:37:48 shown	10101ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 15:57:13	7850ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 18:45:54	3517ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 18:14:25	15020ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 17:58:36	9244ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 17:34:12	11340ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 16:33:08	2590ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 15:36:18	17356ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 07:15:12	2686ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 05:50:48	2551ms	2 NS 0 A 0 MX	❓ Unknown