jamesbaroud.dk

Historical scan 2026-06-18 23:44:26  ·  ← Latest scan
Zone File Timeline & History Scan Now

jamesbaroud.dk is a .dk domain served by 2 nameservers (ns1.dns-parking.com, ns2.dns-parking.com). It was registered on 29 April 2022 (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 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   145ms

A Records#

1 records   92ms
IPTTLPTRASNISP / OrgCIDRCountryCity
2.57.91.91 300s — AS47583 — — — —

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-19 10:52:13
www CNAMEjamesbaroud.dk (all on jamesbaroud.dk)
www vs bare domainSame network
jamesbaroud.dk: 2.57.91.91 (AS47583)
www.jamesbaroud.dk: 2.57.91.91 (AS47583)
WildcardNo

TLSA / DANE#

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

DNSSEC#

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

SOA#

0ms
FieldValue
Serial2026061801
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-02 01:01:19
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2022-04-29
Expires2027-04-28 (159d)

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
145ms
A
92ms
MX
172ms
AAAA
151ms
TXT
438ms
CAA
160ms
HTTPS
121ms
TLSA
65ms
SOA
0ms
MTA-STS
130ms
DNSSEC
145ms
SRV
354ms
Total
1444ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-19 10:52:13 776ms 2 NS 1 A 0 MX Insecure
2026-11-12 12:31:10 1172ms 2 NS 1 A 0 MX Insecure
2026-11-05 14:30:15 979ms 2 NS 1 A 0 MX Insecure
2026-11-02 00:52:13 429ms 2 NS 1 A 0 MX Insecure
2026-10-31 23:14:46 976ms 2 NS 1 A 0 MX Insecure
2026-10-29 14:45:09 1026ms 2 NS 1 A 0 MX Insecure
2026-10-25 19:34:58 1789ms 2 NS 1 A 0 MX Insecure
2026-10-24 10:18:10 563ms 2 NS 1 A 0 MX Insecure
2026-10-22 09:05:22 755ms 2 NS 1 A 0 MX Insecure
2026-10-22 04:32:01 1438ms 2 NS 1 A 0 MX Insecure
2026-10-17 17:38:13 425ms 2 NS 1 A 0 MX Insecure
2026-10-16 16:24:58 1717ms 2 NS 1 A 0 MX Insecure
2026-10-15 15:50:47 768ms 2 NS 1 A 0 MX Insecure
2026-10-08 04:34:56 1124ms 2 NS 1 A 0 MX Insecure
2026-10-02 00:41:52 727ms 2 NS 1 A 0 MX Insecure
2026-09-25 23:24:01 9448ms 2 NS 1 A 0 MX Insecure
2026-09-24 11:05:23 723ms 2 NS 1 A 0 MX Insecure
2026-09-17 18:08:15 867ms 2 NS 1 A 0 MX Insecure
2026-09-11 03:19:56 1030ms 2 NS 1 A 0 MX Insecure
2026-09-06 02:30:36 845ms 2 NS 1 A 0 MX Insecure
2026-08-27 11:07:32 672ms 2 NS 1 A 0 MX Insecure
2026-08-21 02:13:54 8903ms 2 NS 1 A 0 MX Insecure
2026-08-13 11:00:53 976ms 2 NS 1 A 0 MX Insecure
2026-08-07 04:21:37 1085ms 2 NS 1 A 0 MX Insecure
2026-07-30 06:08:07 4819ms 2 NS 1 A 0 MX Insecure