3komputing.dk

📜 Historical scan 2026-07-21 19:08:20 · ← Latest scan

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

3komputing.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 4 March 2004 (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 4027ms

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#

10056ms

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-14 16:53:15

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2004-03-04
Expires	2027-03-31 (159d)

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

4027ms

4029ms

AAAA

4026ms

TXT

20130ms

CAA

4027ms

HTTPS

4027ms

TLSA

69ms

SOA

4026ms

MTA-STS

4034ms

DNSSEC

10056ms

SRV

4030ms

Total

31254ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-26 11:07:25	10158ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-23 08:21:16	2870ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-22 07:54:56	994ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-21 07:41:38	10360ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 06:20:12	11183ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-19 05:54:53	4109ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-18 03:12:21	993ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-16 19:05:09	1491ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-15 11:53:46	2733ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-14 09:24:51	959ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-12 15:50:19	3482ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-10 21:55:20	3491ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-09 19:51:12	2561ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-06 15:40:09	1490ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-30 23:43:53	817ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-29 04:08:43	2875ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-27 21:04:34	890ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-26 20:45:35	849ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-25 20:16:19	916ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-24 19:57:09	899ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-23 19:23:13	907ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-22 19:18:24	933ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-21 19:08:20 shown	31254ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 17:50:46	831ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-19 07:58:14	900ms	2 NS 0 A 0 MX	⚠️ Bogus