apply.dk

Historical scan 2026-06-20 13:22:05  ·  ← Latest scan
Zone File Timeline & History Scan Now

apply.dk is a .dk domain with no delegation in this scan. It was registered on 29 August 2008 (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#

No NS records found

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-11-12 16:43:00
www185.228.232.78 (AS212706) (address records, no CNAME)
www vs bare domainSame network
apply.dk: 185.228.232.78 (AS212706)
www.apply.dk: 185.228.232.78 (AS212706)
WildcardNo

DKIM keys#

1 found
SelectorCNAMEKey
dkim — RSA · ~1024 bit below 2048 bit

DKIM selectors can't be listed, so we check the common ones (Microsoft 365, Google, Mailchimp, SendGrid, generic). Keys under other selectors aren't shown.

TLSA / DANE#

No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

DNSSEC#

8086ms
CheckResult
Validation StatusNot applicable: the domain has no delegation, so there is no zone to validate (stored verdict: Unknown).
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsresolution failed: failure

SOA#

No SOA record found

Registration#

WHOIS fetched 2026-11-02 12:46:24
FieldValue
RegistrarNETIM
Registered2008-08-29
Expires2027-08-31 (285d)

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#

NS
4019ms
A
4017ms
MX
4026ms
AAAA
4026ms
TXT
13783ms
CAA
4017ms
HTTPS
4026ms
TLSA
163ms
SOA
4029ms
MTA-STS
4036ms
DNSSEC
8086ms
SRV
4042ms
Total
18313ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-12 16:43:00 2807ms 2 NS 1 A 1 MX Insecure
2026-11-05 16:22:05 3224ms 2 NS 1 A 1 MX Insecure
2026-11-02 12:41:53 1922ms 2 NS 1 A 1 MX Insecure
2026-10-27 13:37:54 65535ms 2 NS 0 A 1 MX Unknown
2026-10-17 05:22:16 8603ms 2 NS 1 A 1 MX Insecure
2026-10-16 03:48:44 65535ms 2 NS 0 A 0 MX Unknown
2026-10-09 09:41:58 2903ms 2 NS 1 A 1 MX Insecure
2026-10-08 10:07:50 2323ms 2 NS 1 A 1 MX Insecure
2026-09-23 23:50:59 14547ms 2 NS 1 A 1 MX Insecure
2026-09-20 20:07:50 5212ms 2 NS 1 A 1 MX Insecure
2026-09-12 19:49:28 23901ms 2 NS 1 A 1 MX Insecure
2026-07-18 10:55:05 8938ms 2 NS 1 A 1 MX Insecure
2026-07-17 06:16:33 7479ms 2 NS 1 A 1 MX Insecure
2026-07-13 05:05:34 2009ms 2 NS 1 A 1 MX Insecure
2026-06-30 20:14:36 9248ms 2 NS 1 A 1 MX Insecure
2026-06-21 13:06:03 16253ms 2 NS 1 A 1 MX Insecure
2026-06-20 13:22:05 shown 18313ms 0 NS 0 A 0 MX Unknown
2026-06-16 13:37:13 2803ms 2 NS 1 A 1 MX Insecure