ifsudestemg.edu.br security report

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

43risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

9Medium

3Low

1Info

Collected 20 hours ago49.9sfrom cache

Certificate Transparency209
DNS resolution12
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs11
Registration
DNS posture3
Email authentication2
Certificate
Security headers3
Archived URLs
Analysis13

noteFound 209 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
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.

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.ifsudestemg.edu.br/
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.ifsudestemg.edu.br/
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.ifsudestemg.edu.br/
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.ifsudestemg.edu.br/
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.ifsudestemg.edu.br/
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.ifsudestemg.edu.br/
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.ifsudestemg.edu.br/
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.ifsudestemg.edu.br/
Without clientTransferProhibited, a compromised registrar account can move the domain to another registrar in days, with no second step.
What to do
Enable the transfer lock (and registrar lock, if offered) in the registrar control panel.
asset: ifsudestemg.edu.br
gitlab.ifsudestemg.edu.br 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: gitlab.ifsudestemg.edu.br
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.ifsudestemg.edu.br/
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: ifsudestemg.edu.br
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: ifsudestemg.edu.br

final https://www.ifsudestemg.edu.br/status 200time 6411msstack cloudflare · Plone - http://plone.org

–http:// redirects to https://port 80 did not answer
✓Strict-Transport-Security
max-age=31536000
✗Content-Security-Policy
✓Clickjacking protection
SAMEORIGIN, SAMEORIGIN
✓X-Content-Type-Options
nosniff
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✗Cookie __uzma
no Secure · HttpOnly · SameSite=lax
✗Cookie __uzmb
no Secure · HttpOnly · SameSite=lax
✗Cookie __uzme
no Secure · HttpOnly · SameSite=lax
✗Cookie __uzmc
no Secure · HttpOnly · SameSite=lax
✗Cookie __uzmd
no Secure · HttpOnly · SameSite=lax
✗Cookie __uzmf
no Secure · HttpOnly · SameSite=lax
✗Cookie uzmx
no Secure · HttpOnly · SameSite=lax

✓Receives mail via 7 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com aspmx.l.google.com aspmx2.googlemail.com+3
✓SPFends in -all
v=spf1 include:_spf.google.com ip4:200.131.249.12 -all
✓DMARCp=quarantine
v=DMARC1; p=quarantine; rua=mailto:noreply.dmarc@ifsudestemg.edu.br
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
✓CAA
0 iodef "mailto:circ@ifsudestemg.edu.br" · 0 issue "globalsign.com"
–IPv6 (AAAA)IPv4 only
✓3 nameservers
mainecoon.barbacena.ifsudestemg.edu.br odin.jf.ifsudestemg.edu.br shawshank01.ifsudestemg.edu.br

✓Registered16.5 years old
ifsudestemg.edu.br
–Registration expiry
✗Transfer lock
none
✓3 nameservers at registry
mainecoon.barbacena.ifsudestemg.edu.br odin.jf.ifsudestemg.edu.br shawshank01.ifsudestemg.edu.br

Address	Ports	Edge	Network
66.22.76.166 www.ifsudestemg.edu.br +2	80443	direct	—
34.49.159.45 ead.ifsudestemg.edu.br +1	80443	direct	—
200.131.96.36 jf.ifsudestemg.edu.br	80443	direct	—
200.131.249.48 mss.ifsudestemg.edu.br +1	80443	direct	—
66.22.76.180 sig.ifsudestemg.edu.br +4	80443	direct	—
200.131.249.55 idp.ifsudestemg.edu.br	80	direct	—
200.131.249.56 api-gateway.ifsudestemg.edu.br	none known	direct	—
200.131.249.24 gitlab.ifsudestemg.edu.br	none known	direct	—
200.131.249.57 io.ifsudestemg.edu.br	none known	direct	—
200.131.249.44 pgd.ifsudestemg.edu.br	none known	direct	—
200.131.249.36 vsz.ifsudestemg.edu.br	none known	direct	—

Archived URLs

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

ifsudestemg.edu.br security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames