invasi.eu security report

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

25risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

2Medium

3Low

2Info

Collected 5 hours ago184.1sfrom cache

Headers—

unavailable

noteCertificate Transparency did not complete (20). Results below are partial.
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.
noteSecurity headers did not complete (20). Results below are partial.

FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 193.70.57.68:21
Receivers are asked to report spoofing but not to block it. This is the right first step, and the wrong place to stop.
What to do
Once reports look clean, move to p=quarantine, then p=reject.
asset: invasi.eu
193.70.57.68 (invasi.eu) reports php 8.5.9. 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: 193.70.57.68
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 193.70.57.68:25
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: invasi.eu
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: invasi.eu
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: invasi.eu

✓Receives mail via 1 server
in.arubabusiness.it
✓SPFends in -all
v=spf1 a mx include:_spf.arubabusiness.it -all
!DMARCp=none
v=DMARC1; p=none; sp=none; adkim=r; aspf=r; rua=mailto:rua@dmarc.brevo.com
!MTA-STSinbound mail can be downgraded to plaintext

Address	Ports	CVEs	Edge	Network
193.70.57.68 invasi.eu +4	21255380110143443465+5	0	direct	—

Archived URLs

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