servidorprotegido.com security report

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

27risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

1High

0Medium

1Low

2Info

Collected 19 hours ago63.5sfrom cache

Headers—

unavailable

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

SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.servidorprotegido.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@servidorprotegido.com"`, review the reports, then move to p=quarantine and p=reject.
asset: servidorprotegido.com
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: servidorprotegido.com
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: servidorprotegido.com
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: servidorprotegido.com

Address	Ports	CVEs	Edge	Network
177.85.97.13 servidorprotegido.com	none known	0	direct	—

Archived URLs

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