unikaservice.dk

Historical scan 2026-07-24 02:42:27  ·  ← Latest scan
Zone File Timeline & History Scan Now

unikaservice.dk is a .dk domain served by 2 nameservers (ns1.dns-parking.com, ns2.dns-parking.com). It was registered on 1 August 2018 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Its website address 89.116.109.196 is hosted by Hostinger International Limited (AS47583) in United Kingdom. Mail is handled by mx1.titan.email, mx2.titan.email. 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   57ms

A Records#

2 records   55ms

MX Records#

2 records   229ms

AAAA Records (IPv6)#

2 records   55ms

HTTPS Records#

No HTTPS RR — no SVCB/HTTPS service binding

TXT Records#

1 records   437ms
TXT Record
v=spf1 include:spf.titan.email ~all

SPF#

PolicyRecord (unikaservice.dk)
~all (soft fail) v=spf1 include:spf.titan.email ~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 23:41:20

DNS lookups: 4/10 · policy: ~all

No problems found

TLSA / DANE#

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

DNSSEC#

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

SOA#

0ms
FieldValue
Serial2026072301
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-05 09:24:03
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2018-08-01
Expires2027-08-31 (286d)

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
57ms
A
55ms
MX
229ms
AAAA
55ms
TXT
437ms
CAA
57ms
HTTPS
58ms
TLSA
162ms
SOA
0ms
MTA-STS
91ms
DNSSEC
9065ms
SRV
88ms
Total
10064ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-12 23:41:20 1650ms 2 NS 2 A 2 MX Insecure
2026-11-05 04:32:42 1215ms 2 NS 2 A 2 MX Insecure
2026-10-29 06:47:49 1012ms 2 NS 2 A 2 MX Insecure
2026-10-28 00:08:52 1322ms 2 NS 2 A 2 MX Insecure
2026-10-22 14:09:23 973ms 2 NS 2 A 2 MX Insecure
2026-10-15 22:35:49 1206ms 2 NS 2 A 2 MX Insecure
2026-10-08 21:52:11 987ms 2 NS 2 A 2 MX Insecure
2026-10-01 20:19:34 726ms 2 NS 2 A 2 MX Insecure
2026-09-29 20:05:42 1086ms 2 NS 2 A 2 MX Insecure
2026-09-24 12:21:05 1088ms 2 NS 2 A 2 MX Insecure
2026-09-17 23:20:36 1704ms 2 NS 2 A 2 MX Insecure
2026-09-12 10:27:20 1117ms 2 NS 2 A 2 MX Insecure
2026-09-04 08:51:20 1987ms 2 NS 2 A 2 MX Insecure
2026-08-31 16:43:23 2213ms 2 NS 2 A 2 MX Insecure
2026-08-27 09:41:01 10048ms 2 NS 2 A 2 MX Insecure
2026-08-20 03:11:01 10454ms 2 NS 2 A 2 MX Insecure
2026-08-13 04:54:35 10225ms 2 NS 2 A 2 MX Insecure
2026-08-08 04:54:09 1903ms 2 NS 2 A 2 MX Insecure
2026-07-31 09:51:25 17123ms 2 NS 2 A 2 MX Insecure
2026-07-24 02:42:27 shown 10064ms 2 NS 2 A 2 MX Insecure
2026-07-16 11:43:40 1225ms 2 NS 2 A 2 MX Insecure
2026-07-10 16:57:12 1489ms 2 NS 2 A 2 MX Insecure
2026-07-03 18:40:14 2337ms 2 NS 2 A 2 MX Insecure
2026-06-29 09:35:01 1267ms 2 NS 2 A 2 MX Insecure
2026-06-25 10:30:19 1050ms 2 NS 2 A 2 MX Insecure