securecode.dk
Historical scan 2026-08-16 22:24:39 · ← Latest scan
securecode.dk is a registered .dk domain whose nameservers (ns1.nameservices.us, ns2.nameservices.us) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 9 December 2002 (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 4147ms| Nameserver | IP addresses | PTR | ASN / ISP |
|---|---|---|---|
| ns1.nameservices.us | — | — | — |
| ns2.nameservices.us | — | — | — |
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
Web & zone#
latest probe, not this scan · checked 2026-10-05 05:11:37| www | Address record (no CNAME) |
| Wildcard | Yes: any name under the zone resolves |
TLSA / DANE#
No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)
DNSSEC#
10267ms| 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: timed out |
SOA#
No SOA record found
Registration#
WHOIS fetched 2026-11-07 05:21:01| Field | Value |
|---|---|
| Registrar | CSC Digital Brand Service, Inc |
| Registered | 2002-12-09 |
| Expires | 2026-12-31 (43d) |
Same registrant#
45 domainsOther .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).
📋 WHOIS#
Lookup Timing#
NS
A
MX
AAAA
TXT
CAA
HTTPS
TLSA
SOA
MTA-STS
DNSSEC
SRV
Total
Scan History#
| Scanned At | Duration | Records | DNSSEC |
|---|---|---|---|
| 2026-10-06 05:19:12 | 1103ms | 2 NS 0 A 0 MX | Unknown |
| 2026-10-05 05:11:37 | 3277ms | 2 NS 1 A 1 MX | Insecure |
| 2026-10-03 05:03:30 | 2698ms | 2 NS 1 A 1 MX | Insecure |
| 2026-10-02 05:03:03 | 4115ms | 2 NS 1 A 1 MX | Insecure |
| 2026-10-01 04:53:42 | 3658ms | 2 NS 1 A 1 MX | Insecure |
| 2026-09-30 04:45:38 | 3389ms | 2 NS 1 A 1 MX | Insecure |
| 2026-09-29 04:30:59 | 3512ms | 2 NS 1 A 1 MX | Insecure |
| 2026-09-28 04:18:20 | 3274ms | 2 NS 1 A 1 MX | Insecure |
| 2026-09-27 03:58:42 | 3166ms | 2 NS 1 A 1 MX | Insecure |
| 2026-09-26 03:39:45 | 3184ms | 2 NS 1 A 1 MX | Insecure |
| 2026-09-25 03:11:11 | 3232ms | 2 NS 1 A 1 MX | Insecure |
| 2026-09-24 02:03:30 | 3267ms | 2 NS 1 A 1 MX | Insecure |
| 2026-09-20 08:39:48 | 9462ms | 2 NS 1 A 1 MX | Insecure |
| 2026-09-13 07:25:56 | 9978ms | 2 NS 1 A 1 MX | Insecure |
| 2026-09-06 06:48:40 | 3251ms | 2 NS 1 A 1 MX | Insecure |
| 2026-09-03 23:34:31 | 3134ms | 2 NS 1 A 1 MX | Insecure |
| 2026-08-31 05:06:14 | 4102ms | 2 NS 1 A 1 MX | Insecure |
| 2026-08-29 13:08:38 | 3180ms | 2 NS 1 A 1 MX | Insecure |
| 2026-08-28 02:27:05 | 3090ms | 2 NS 1 A 1 MX | Insecure |
| 2026-08-27 01:59:21 | 3285ms | 2 NS 1 A 1 MX | Insecure |
| 2026-08-23 21:50:14 | 65535ms | 2 NS 0 A 0 MX | Unknown |
| 2026-08-22 17:04:33 | 65535ms | 2 NS 0 A 0 MX | Unknown |
| 2026-08-21 16:59:18 | 65535ms | 2 NS 0 A 0 MX | Unknown |
| 2026-08-20 16:49:17 | 65535ms | 2 NS 0 A 0 MX | Unknown |
| 2026-08-19 16:17:16 | 65535ms | 2 NS 0 A 0 MX | Unknown |