loopcraft.dk

Historical scan 2026-11-11 08:36:47  ·  ← Latest scan
Zone File Timeline & History Scan Now

loopcraft.dk is a .dk domain served by 2 nameservers (dns103.ovh.net, ns103.ovh.net). It was registered on 10 November 2026 (WHOIS) and first appeared in the .dk zone on 11 November 2026. Mail is handled by mx1.mail.ovh.net, mx2.mail.ovh.net and 1 more. The zone is not DNSSEC-signed, publishes a 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   53ms

A Records#

No A records found

MX Records#

3 records   62ms

AAAA Records (IPv6)#

No AAAA records — IPv6 not configured

HTTPS Records#

No HTTPS RR — no SVCB/HTTPS service binding

TXT Records#

2 records   276ms
TXT Record
brevo-code:66022a400916bedb43a9f456dafb3c50
v=spf1 include:mx.ovh.com include:spf.brevo.com ~all

SPF#

PolicyRecord (loopcraft.dk)
~all (soft fail) v=spf1 include:mx.ovh.com include:spf.brevo.com ~all

DMARC#

PolicyRecord (_dmarc.loopcraft.dk)
p=none (monitor only) v=DMARC1; p=none; rua=mailto:rua@dmarc.brevo.com

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 14:49:15

DNS lookups: 4/10 · policy: ~all

No problems found

TLSA / DANE#

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

DNSSEC#

76ms
CheckResult
Validation Status Insecure
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Not found
Flagsresolution failed: ncache nxrrset

SOA#

44ms
FieldValue
Serial2094382148
Primary NS (MNAME)dns103.ovh.net
Responsible (RNAME)tech@ovh.net
Refresh86400s
Retry3600s
Expire3600000s
Minimum (neg-cache TTL)60s

Registration#

WHOIS fetched 2026-11-17 10:51:34
FieldValue
RegistrarOvh
Registered2026-11-10
Expires2027-11-09 (356d)

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
53ms
A
54ms
MX
62ms
AAAA
52ms
TXT
276ms
CAA
63ms
HTTPS
51ms
TLSA
63ms
SOA
44ms
MTA-STS
87ms
DNSSEC
76ms
SRV
83ms
Total
502ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-13 14:49:15 1397ms 2 NS 4 A 3 MX Insecure
2026-11-12 14:42:35 968ms 2 NS 4 A 3 MX Insecure
2026-11-11 08:36:47 shown 502ms 2 NS 0 A 3 MX Insecure