alma-copenhagen.dk

Historical scan 2026-09-19 01:15:02  ·  ← Latest scan
Zone File Timeline & History Scan Now

alma-copenhagen.dk is a .dk domain served by 2 nameservers (ns1.dns-parking.com, ns2.dns-parking.com). It was registered on 3 September 2025 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Its website address 23.227.38.65 is hosted by Cloudflare, Inc. (AS13335) in Canada. Mail is handled by mx.zoho.eu, mx2.zoho.eu and 1 more. The zone is not DNSSEC-signed, has no DMARC policy and has no IPv6 address. 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   60ms

A Records#

1 records   60ms

MX Records#

3 records   68ms

AAAA Records (IPv6)#

No AAAA records — IPv6 not configured

HTTPS Records#

No HTTPS RR — no SVCB/HTTPS service binding

TXT Records#

1 records   488ms
TXT Record
v=spf1 include:zohomail.eu ~all

SPF#

PolicyRecord (alma-copenhagen.dk)
~all (soft fail) v=spf1 include:zohomail.eu ~all

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 13:58:53

DNS lookups: 2/10 · policy: ~all

No problems found

TLSA / DANE#

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

DNSSEC#

136ms
CheckResult
Validation Status Insecure
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsunsigned answer

SOA#

0ms
FieldValue
Serial2026091701
Primary NS (MNAME)ns1.dns-parking.com
Responsible (RNAME)dns@hostinger.com
Refresh10000s
Retry2400s
Expire604800s
Minimum (neg-cache TTL)600s

Registration#

WHOIS fetched 2026-11-12 14:01:45
FieldValue
RegistrarRealtime Register B.V.
Registered2025-09-03
Expires2027-09-02 (287d)

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
60ms
A
60ms
MX
68ms
AAAA
798ms
TXT
488ms
CAA
51ms
HTTPS
61ms
TLSA
218ms
SOA
0ms
MTA-STS
91ms
DNSSEC
136ms
SRV
318ms
Total
2038ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-12 13:58:53 1945ms 2 NS 1 A 3 MX Insecure
2026-11-05 21:40:04 1118ms 2 NS 1 A 3 MX Insecure
2026-11-05 21:38:50 3402ms 2 NS 1 A 3 MX Insecure
2026-10-30 16:01:13 1244ms 2 NS 1 A 3 MX Insecure
2026-10-22 23:07:56 1442ms 2 NS 1 A 3 MX Insecure
2026-10-15 04:44:24 1807ms 2 NS 1 A 3 MX Insecure
2026-10-08 15:34:11 3142ms 2 NS 1 A 3 MX Insecure
2026-10-01 09:10:45 2247ms 2 NS 1 A 3 MX Insecure
2026-09-25 07:23:39 979ms 2 NS 1 A 3 MX Insecure
2026-09-25 02:44:12 2133ms 2 NS 1 A 3 MX Insecure
2026-09-19 01:15:02 shown 2038ms 2 NS 1 A 3 MX Insecure
2026-09-11 15:00:45 1618ms 2 NS 1 A 3 MX Insecure
2026-09-04 13:32:08 2435ms 2 NS 1 A 3 MX Insecure
2026-08-28 04:16:06 1536ms 2 NS 1 A 3 MX Insecure
2026-08-20 23:25:48 1716ms 2 NS 1 A 3 MX Insecure
2026-08-13 06:39:28 9841ms 2 NS 1 A 3 MX Insecure
2026-08-09 16:58:51 2532ms 2 NS 1 A 3 MX Insecure
2026-08-03 02:23:55 2457ms 2 NS 1 A 3 MX Insecure
2026-07-23 23:27:20 10305ms 2 NS 1 A 3 MX Insecure
2026-07-16 10:04:43 1517ms 2 NS 1 A 3 MX Insecure
2026-07-13 22:37:45 1249ms 2 NS 1 A 3 MX Insecure
2026-07-03 15:10:22 2276ms 2 NS 1 A 3 MX Insecure
2026-06-28 17:27:51 1279ms 2 NS 1 A 3 MX Insecure
2026-06-18 10:15:35 3503ms 2 NS 1 A 3 MX Insecure
2026-06-16 12:55:55 1472ms 2 NS 1 A 3 MX Insecure