metrodoporto.pt security report

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

45risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

1High

2Medium

3Low

2Info

Collected 16 hours ago80.2sfrom cache

Certificate Transparency6
DNS resolution8
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs31
Registration
DNS posture2
Email authentication2
Certificate
Security headers2
Archived URLs
Analysis8

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.

A visitor who types the address without https, or follows an old link, gets the unencrypted site. On public Wi-Fi that page can be read and rewritten in transit.
What to do
Redirect every http:// request to https:// with a 301, then add HSTS.
asset: https://metrodoporto.pt/
Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://metrodoporto.pt/
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://metrodoporto.pt/
5.249.117.22 (webmail.metrodoporto.pt) reports internet information services 10.0, outlook web access 15.2.1544, asp.net 4.0.30319. 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: 5.249.117.22
Lets browsers guess content types, which turns some upload and text endpoints into script injection points.
What to do
Send `X-Content-Type-Options: nosniff` on every response.
asset: https://metrodoporto.pt/
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: metrodoporto.pt
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: metrodoporto.pt
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: metrodoporto.pt

final https://metrodoporto.pt/status 520time 354msstack cloudflare

✗http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✓Clickjacking protection
SAMEORIGIN
✗X-Content-Type-Options
✓Referrer-Policy
same-origin
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 1 server
metrodoporto.in.tmes.trendmicro.eu
✓SPFends in -all
v=spf1 mx a:smtp1.metro-porto.pt a:smtp2.metro-porto.pt a:smtp3.metro-porto.pt a:smtpx.wiremaze.com include:spf.tmes.trendmicro.com include:spf.protection.outlook.com -all
✓DMARCp=reject
v=DMARC1; p=reject; pct=100; ruf=mailto:gsiadmin@metrodoporto.pt; rua=mailto:gsiadmin@metrodoporto.pt; adkim=r; aspf=r
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
coraline.ns.cloudflare.com martin.ns.cloudflare.com

Address	Ports	Edge	Network
172.66.157.20 doc.metrodoporto.pt +3	80443205220532082208320862087+5	Cloudflare~	—
104.20.26.93 doc.metrodoporto.pt +3	80443205220532082208320862087+5	Cloudflare~	—
193.126.238.123 metrodoporto.pt +2	80443	direct	—
5.249.117.23 mft.metrodoporto.pt +1	44350000	direct	—
5.249.117.22 webmail.metrodoporto.pt +3	443	direct	—

Archived URLs

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

metrodoporto.pt security report

Moderate

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames