Digital exposure report
pucpr.br
Good shape, with a few gaps worth closing this quarter.
Scanned: 2026-11-22 15:02 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
List the servers allowed to send your email
Without this list, it is easier for others to send email that looks like it came from you.
Who can fix it: Your email provider, together with whoever manages your DNS
How to verify after the fix
dig +short TXT pucpr.br
- 2.
Choose which companies may issue certificates for your domain
This reduces the chance of a certificate being issued by a provider you did not choose.
Who can fix it: Your domain registrar or DNS provider
How to verify after the fix
dig +short CAA pucpr.br
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- pucpr.br
- Website request
- GET https://pucpr.br/ → https://www.pucpr.br/
- Scan time
- 2026-11-22 15:02:39 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- None. Every applicable check was assessed.
This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.
Score by category
| Email security | 22/30 | Spoofing email in the company's name is possible in some cases. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 27/30 | The site instructs browsers to block common attacks. |
| DNS infrastructure | 10/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.MediumSPF — who may send mail for the domain · Hardening gap+6
- 2.LowCAA — who may issue certificates · Hardening gap+5
- 3.LowCSP — protection from script injection · Hardening gap+3
Findings
SPF — who may send mail for the domain
Needs attention · Severity: Medium · Hardening gap · 4/10The SPF record has no instruction for unauthorized senders.
No all mechanism and no redirect= found, so the default is neutral.
v=spf1 include:spf0.pucpr.br
$ dig +short TXT pucpr.br
- Map every service that sends mail in the domain's name (Google Workspace / Microsoft 365, newsletter tool, CRM).
- Publish exactly one TXT record at the domain root starting with v=spf1.
- Start with ~all, and move to -all once DMARC reports confirm all legitimate senders are covered.
pucpr.br. TXT "v=spf1 include:_spf.google.com ~all"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. An incorrect record can block legitimate mail — add every sender before tightening.
DMARC — anti-spoofing policy
Passed · Severity: OK · 13/15Forged email in the company's name is sent to the spam folder.
Policy p=quarantine. p=quarantine — consider moving to p=reject.
v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@grupomarista.org.br; ruf=mailto:dmarc@grupomarista.org.br
$ dig +short TXT _dmarc.pucpr.br
DKIM — digital signature on email
Passed · Severity: OK · 5/5A DKIM public key is published. On its own this doesn't prove outgoing mail is signed or aligned with your From domain.
DKIM public key found for selector: selector1, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
selector1._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuQhwZoGVFwzM62ynHQz7AFeKCzA0… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAun5ki0CRgMfyHGLxAlhnyHw9wGShlYlL… s2._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzbem6VkPyGWl0gO5udzvXq3ZMqSl8pC2…
$ dig +short TXT selector1._domainkey.pucpr.br
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
1 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
0 pucpr-br.mail.protection.outlook.com
$ dig +short MX pucpr.br
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://pucpr.br/ returned HTTP 200 (final URL: https://www.pucpr.br/). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.pucpr.br/
$ curl -sIL https://pucpr.br/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://pucpr.br/
HTTP 301 Location: https://pucpr.br/
$ curl -sI http://pucpr.br/ | grep -iE "^(HTTP|location)"
SSL/TLS certificate validity
Passed · Severity: OK · 8/8The certificate was accepted by a validating TLS client at scan time.
Live TLS handshake succeeded. Latest issuance in CT logs: DigiCert, expiring 2027-03-07 (105 days). CT shows issued certificates, not necessarily the one served — confirm dates with the verify command.
Live TLS handshake: certificate accepted CT logs (context only, not scored): Issuer: DigiCert Valid from: 2026-02-04 Valid until: 2027-03-07 Names: *.pucpr.br, 3rdauth.pucpr.br, adhafera.pucpr.br, afpuc.pucpr.br, agendadocente.pucpr.br, agiledeploy.pucpr.br Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect pucpr.br:443 -servername pucpr.br 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Passed · Severity: OK · 8/8Browsers are told to always use an encrypted connection to the site.
max-age=31536000 (365 days), includeSubDomains. ≥ 180 days recommended.
Strict-Transport-Security: max-age=31536000; includeSubDomains
$ curl -sIL https://pucpr.br/ | grep -i "Strict-Transport-Security"
CSP — protection from script injection
Needs attention · Severity: Low · Hardening gap · 5/8A script policy exists, but it's permissive and offers only partial protection.
script-src includes: 'unsafe-inline', 'unsafe-eval', a broad source (* / https: / data:) — weakens XSS protection.
Content-Security-Policy: default-src * *.com *.br blob: data: *.ai 'unsafe-inline' 'unsafe-eval'
$ curl -sIL https://pucpr.br/ | grep -i "Content-Security-Policy"
- First publish Content-Security-Policy-Report-Only — it blocks nothing, it only reports.
- Collect violations for a week or two and tune the policy to your legitimate sources.
- Switch to the Content-Security-Policy header and replace 'unsafe-inline' with a nonce or hash.
/* Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'
Safety: This change is made in your server/CDN settings. Test on staging before production. An overly strict CSP will break scripts — that's why you start in Report-Only mode.
Clickjacking protection
Passed · Severity: OK · 5/5The site can't be embedded by foreign sites.
X-Frame-Options: SAMEORIGIN
X-Frame-Options: SAMEORIGIN
$ curl -sIL https://pucpr.br/ | grep -i "X-Frame-Options"
X-Content-Type-Options
Passed · Severity: OK · 4/4The browser won't guess file types in a way that could execute code.
nosniff is set.
X-Content-Type-Options: nosniff
$ curl -sIL https://pucpr.br/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Passed · Severity: OK · 3/3Internal URLs don't leak to external sites.
Referrer-Policy: origin-when-cross-origin
Referrer-Policy: origin-when-cross-origin
$ curl -sIL https://pucpr.br/ | grep -i "Referrer-Policy"
Permissions-Policy
Passed · Severity: OK · 2/2The site restricts access to sensitive browser features.
Permissions-Policy: accelerometer=(),autoplay=(),camera=(),encrypted-media=(),fullscreen=*,geolocation=*,gyroscope=(),interest-cohort=(),magnetometer=(),microphone=(),midi=(),payme
Permissions-Policy: accelerometer=(),autoplay=(),camera=(),encrypted-media=(),fullscreen=*,geolocation=*,gyroscope=(),interest-cohort=(),magnetometer=(),microphone=(),midi=(),payment=("https://*.paypal.com" "https://*.barion.com"),sync-xhr=*,usb=(),xr-spatial-tracking=()$ curl -sIL https://pucpr.br/ | grep -i "Permissions-Policy"
Software version disclosure
Passed · Severity: OK · unscoredThe server doesn't disclose software versions.
No version numbers found in the Server / X-Powered-By headers.
server: cloudflare x-powered-by: (missing)
$ curl -sIL https://pucpr.br/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Passed · Severity: OK · 7/7The domain's records are digitally signed and hard to forge.
An AD (Authenticated Data) flag was returned by a validating resolver.
AD = true
$ dig +dnssec pucpr.br | grep -E "flags:.* ad"
CAA — who may issue certificates
Needs attention · Severity: Low · Hardening gap · 0/5Any certificate authority can issue a certificate for the domain, raising the risk of mis-issuance.
No CAA records found. RFC 8659 lets the domain owner restrict which CAs are authorized.
(no CAA records found)
$ dig +short CAA pucpr.br
- Identify which certificate authority issued your current certificate (see the certificate check).
- Publish CAA for that authority only, and add iodef to receive alerts.
pucpr.br. CAA 0 issue "letsencrypt.org" pucpr.br. CAA 0 iodef "mailto:security@pucpr.br"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. If your CDN issues certificates on your behalf, include it too — otherwise certificate renewal will fail.
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
2 NS servers.
guss.ns.cloudflare.com alice.ns.cloudflare.com
$ dig +short NS pucpr.br
Indicative alignment
Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.
- Google & Yahoo sender rules1 observed gaps
- PCI DSS v4.01 observed gaps
- NIS2 / vendor due diligence2 observed gaps
- SOC 2 / ISO 27001 baseline2 observed gaps
Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.
Public DNS records
| A | pucpr.br | 104.18.10.132 | 104.18.11.132 |
| AAAA | pucpr.br | 2606:4700::6812:a84 | 2606:4700::6812:b84 |
| MX | pucpr.br | 0 pucpr-br.mail.protection.outlook.com |
| NS | pucpr.br | guss.ns.cloudflare.com | alice.ns.cloudflare.com |
| TXT | pucpr.br | hgkbjjlj3cu6c2oa8mfmutan80 | tjfkecadoegq3m3frvnuol86e5 | v=spf1 include:spf0.pucpr.br | preprojeto2.azurewebsites.net | 4w02y6jw5d7dzkz66vfjf4dpzr9sp8cr | apple-domain-verification=l2gzowxuJR3w7C13 | bw=CZhbmREjGq2aOkYt7CTtOEMlEDytZgQMQGQrrbJcHey9 | amazonses:qR9t41SDyar2l2zT9YAQt3n7aVmjShPzu6KKNEZz6zI= | have-i-been-pwned-verification=5e2c2a890cdb081999beec8b151d6947 | google-site-verification=pk9Adv8BiMeI1BpCSkDVX6iWd_ryzlN5OEaWVFvxgqk | google-site-verification=qxiz0_JdsW9DH03Dfo-ijKjp7AtVglKwvU7a4hyPkU4 | tinfoil-site-verification: c457e0ccb8d6d7f1fad4503a27830efec7b97ce9=9e3e952fa4a8feb280ac49afa4262a212999cec1 |
| TXT | _dmarc.pucpr.br | v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@grupomarista.org.br; ruf=mailto:dmarc@grupomarista.org.br |
| CAA | pucpr.br | — |
| DS | pucpr.br | 2371 13 2 8db27a6073e16e1f02e9851f0e07fa292e724f73b88a1f4e0fa6d30162e26382 |