selo.dk

Historical scan 2026-10-15 14:59:48  ·  ← Latest scan
Zone File Timeline & History Scan Now

selo.dk is a .dk domain served by 2 nameservers (ns1.dns-parking.com, ns2.dns-parking.com). It was registered on 15 May 2007 (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 selo.dk. The zone is not DNSSEC-signed, has no DMARC policy and is reachable over IPv6. 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   138ms

A Records#

1 records   141ms

MX Records#

1 records   119ms

AAAA Records (IPv6)#

1 records   112ms
IPv6 AddressTTLPTRASNISP / OrgCIDRCountryCity
2620:127:f00f:5:: 3600s — AS13335 Cloudflare, Inc. 2620:127:f00c:0:0:0:0:0/46 🇨🇦 Canada —

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-15 02:03:16

TLSA / DANE#

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

DNSSEC#

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

SOA#

88ms
FieldValue
Serial2026101501
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-13 05:47:27
FieldValue
RegistrarRealtime Register B.V.
Registered2007-05-15
Expires2027-05-31 (195d)

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
138ms
A
141ms
MX
119ms
AAAA
112ms
TXT
450ms
CAA
107ms
HTTPS
139ms
TLSA
1720ms
SOA
88ms
MTA-STS
173ms
DNSSEC
711ms
SRV
294ms
Total
3044ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-15 02:03:16 1025ms 2 NS 2 A 1 MX Insecure
2026-11-14 01:57:15 1428ms 2 NS 2 A 1 MX Insecure
2026-11-13 00:54:18 1487ms 2 NS 2 A 1 MX Insecure
2026-11-05 07:24:43 965ms 2 NS 2 A 1 MX Insecure
2026-10-30 02:28:25 1096ms 2 NS 1 A 1 MX Insecure
2026-10-24 11:50:09 737ms 2 NS 1 A 1 MX Insecure
2026-10-15 14:59:48 shown 3044ms 2 NS 1 A 1 MX Insecure
2026-10-09 01:05:24 2746ms 2 NS 1 A 1 MX Insecure
2026-10-01 23:28:58 3162ms 2 NS 1 A 1 MX Insecure
2026-09-30 23:19:36 785ms 2 NS 1 A 1 MX Insecure
2026-09-24 05:10:33 9423ms 2 NS 1 A 1 MX Insecure
2026-09-19 20:05:44 1702ms 2 NS 1 A 1 MX Insecure
2026-09-13 07:33:19 1298ms 2 NS 1 A 1 MX Insecure
2026-09-03 18:54:25 824ms 2 NS 1 A 1 MX Insecure
2026-08-28 02:20:06 893ms 2 NS 1 A 1 MX Insecure
2026-08-27 01:51:23 9644ms 2 NS 1 A 1 MX Insecure
2026-08-20 13:13:00 10251ms 2 NS 1 A 1 MX Insecure
2026-08-14 13:34:52 836ms 2 NS 1 A 1 MX Insecure
2026-08-09 16:11:04 1549ms 2 NS 1 A 1 MX Insecure
2026-08-02 02:57:42 1030ms 2 NS 1 A 1 MX Insecure
2026-07-23 14:45:06 2064ms 2 NS 1 A 1 MX Insecure
2026-07-16 18:52:50 1037ms 2 NS 1 A 1 MX Insecure
2026-07-10 16:23:24 1213ms 2 NS 1 A 1 MX Insecure
2026-07-03 15:48:24 797ms 2 NS 1 A 1 MX Insecure
2026-06-29 01:50:35 807ms 2 NS 1 A 1 MX Insecure