motostorm.it security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

41risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

3Medium

8Low

1Info

Collected 17 hours ago4.6sfrom cache

Certificate Transparency21
DNS resolution14
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs39
Registration
DNS posture2
Email authentication2
Certificate
Security headers3
Archived URLs
Analysis12

noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.
noteNo registration data: RDAP has no record at this level.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 185.221.172.96:21
CSP is the main defence that limits what an injected script can do. Without it, any XSS bug is fully exploitable.
What to do
Start with a report-only policy, tighten it against the reports, then enforce.
asset: https://www.motostorm.it/it/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://www.motostorm.it/it/
185.221.172.96 (mail2.motostorm.it) reports exim 4.99.5. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 185.221.172.96
admin.motostorm.it appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: admin.motostorm.it
staging.motostorm.it appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: staging.motostorm.it
Browsers and the preload list expect at least six months; shorter values give little protection between visits.
What to do
Raise max-age to 31536000 (one year).
asset: https://www.motostorm.it/it/
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://www.motostorm.it/it/
Exact versions in response headers let anyone match the server against a CVE feed without touching it.
What to do
Strip version tokens (`ServerTokens Prod`, `server_tokens off`, remove X-Powered-By).
asset: https://www.motostorm.it/it/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://www.motostorm.it/it/
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: motostorm.it
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: motostorm.it

final https://www.motostorm.it/it/status 200time 618msstack cloudflare · PHP/8.3.33, PleskLin

✓http:// redirects to https://
!Strict-Transport-Security
max-age=15552000; preload
✗Content-Security-Policy
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✗Cookie motostorm
no Secure · no HttpOnly · no SameSite

✓Receives mail via 1 server
mail.motostorm.it
✓SPFends in -all
v=spf1 +a +mx -all +a:d01itg-motostorm.sphostserver.com
✓DMARCp=quarantine
v=DMARC1; p=quarantine;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
✓CAA
0 issue "comodoca.com" · 0 issue "digicert.com; cansignhttpexchanges=yes" · 0 issue "letsencrypt.org" · 0 issue "pki.goog; cansignhttpexchanges=yes" · 0 issue "ssl.com" · 0 issuewild "comodoca.com" · 0 issuewild "digicert.com; cansignhttpexchanges=yes" · 0 issuewild "letsencrypt.org" · 0 issuewild "pki.goog; cansignhttpexchanges=yes" · 0 issuewild "ssl.com"
✓IPv6 (AAAA)
✓2 nameservers
adel.ns.cloudflare.com curt.ns.cloudflare.com

Address	Ports	Edge	Network
185.221.172.96 mail2.motostorm.it +7	215380110143443465993+6	direct	—
172.66.40.79 motostorm.it +7	80443205220532082208320862087+5	Cloudflare~	—
172.66.43.177 motostorm.it +7	80443205220532082208320862087+4	Cloudflare~	—
46.28.2.173 mail.motostorm.it +1	none known	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

motostorm.it security report

Moderate

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames