3style.dk

📜 Historical scan 2026-08-21 14:25:06 · ← Latest scan

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

3style.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 November 2007 (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 65ms

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#

291ms

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-19 15:12:04

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2007-11-02
Expires	2026-11-30 (38d)

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

65ms

78ms

80ms

AAAA

66ms

TXT

255ms

CAA

68ms

HTTPS

67ms

TLSA

96ms

SOA

67ms

MTA-STS

116ms

DNSSEC

291ms

SRV

127ms

Total

1359ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-02 15:51:11	3423ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-01 12:41:32	2724ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-01 04:50:19	10079ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 04:45:14	1514ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 14:52:12	3021ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 14:36:32	27268ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 14:25:06 shown	1359ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 14:16:36	5283ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:14:37	1655ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 02:40:20	3550ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 10:51:49	5463ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 07:05:30	10119ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 13:41:56	3603ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 23:15:21	909ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 17:29:52	2839ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 17:58:24	2549ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 17:49:23	10098ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 17:15:22	1010ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 16:49:15	1042ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 16:18:32	8948ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 14:55:53	1074ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 16:07:59	877ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 14:30:28	918ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 06:13:52	2851ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 04:02:40	1045ms	2 NS 0 A 0 MX	❓ Unknown