fri-jobber.dk

Historical scan 2026-09-24 22:54:40  ·  ← Latest scan
Zone File Timeline & History Scan Now

fri-jobber.dk is a .dk domain served by 2 nameservers (ns1.dns-parking.com, ns2.dns-parking.com). It was registered on 10 December 2025 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. 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   65ms

A Records#

2 records   60ms
IPTTLPTRASNISP / OrgCIDRCountryCity
217.65.156.162 60s — AS47583 — — 🇩🇪 Germany —
217.65.159.91 60s — AS47583 — — 🇩🇪 Germany —

MX Records#

No MX records found

AAAA Records (IPv6)#

2 records   63ms
IPv6 AddressTTLPTRASNISP / OrgCIDRCountryCity
2a02:4780:7f:cca2:2397:b7a2:d583:d463 60s — AS47583 — — 🇨🇾 Cyprus —
2a02:4780:80:9b91:5e79:3556:cd42:7ec5 60s — AS47583 — — 🇨🇾 Cyprus —

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-13 00:22:13

TLSA / DANE#

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

DNSSEC#

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

SOA#

0ms
FieldValue
Serial2026092401
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 07:36:30
FieldValue
RegistrarRealtime Register B.V.
Registered2025-12-10
Expires2026-12-09 (21d)

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
65ms
A
60ms
MX
53ms
AAAA
63ms
TXT
347ms
CAA
64ms
HTTPS
61ms
TLSA
90ms
SOA
0ms
MTA-STS
108ms
DNSSEC
132ms
SRV
385ms
Total
870ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-13 00:22:13 724ms 2 NS 2 A 0 MX Insecure
2026-11-05 07:02:38 890ms 2 NS 2 A 0 MX Insecure
2026-10-30 02:19:29 1398ms 2 NS 2 A 0 MX Insecure
2026-10-23 10:58:29 844ms 2 NS 2 A 0 MX Insecure
2026-10-15 22:26:54 1647ms 2 NS 2 A 0 MX Insecure
2026-10-08 06:15:13 893ms 2 NS 2 A 0 MX Insecure
2026-10-02 00:34:55 679ms 2 NS 2 A 0 MX Insecure
2026-09-24 22:54:40 shown 870ms 2 NS 2 A 0 MX Insecure
2026-09-19 15:10:06 4666ms 2 NS 2 A 0 MX Insecure
2026-09-13 11:02:12 1135ms 2 NS 2 A 0 MX Insecure
2026-09-03 17:10:44 915ms 2 NS 2 A 0 MX Insecure
2026-08-27 15:36:42 700ms 2 NS 2 A 0 MX Insecure
2026-08-20 04:41:35 3235ms 2 NS 2 A 0 MX Insecure
2026-08-15 04:55:32 997ms 2 NS 2 A 0 MX Insecure
2026-08-06 09:14:18 1049ms 2 NS 2 A 0 MX Insecure
2026-07-31 11:34:15 1313ms 2 NS 2 A 0 MX Insecure
2026-07-23 03:09:33 691ms 2 NS 2 A 0 MX Insecure
2026-07-16 21:31:43 9542ms 2 NS 2 A 0 MX Insecure
2026-07-10 20:26:16 1061ms 2 NS 2 A 0 MX Insecure
2026-07-03 05:03:10 1092ms 2 NS 2 A 0 MX Insecure
2026-06-25 20:34:11 673ms 2 NS 2 A 0 MX Insecure
2026-06-20 09:36:01 909ms 2 NS 2 A 0 MX Insecure
2026-06-17 10:35:41 613ms 2 NS 2 A 0 MX Insecure
2026-06-17 10:28:44 734ms 2 NS 2 A 0 MX Insecure