Digital exposure report
upf.edu
Good shape, with a few gaps worth closing this quarter.
Scanned: 2026-11-19 04:57 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Limit what scripts your pages are allowed to run
This adds one layer of protection against injected scripts.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://upf.edu/ | grep -i "Content-Security-Policy"
- 2.
Limit what your site shares when visitors click links
This reduces how much page address detail is passed to other websites.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://upf.edu/ | grep -i "Referrer-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- upf.edu
- Website request
- GET https://upf.edu/ → https://www.upf.edu/
- Scan time
- 2026-11-19 04:57:58 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 | 28/30 | Spoofing email from this domain is hard. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 16/30 | Some browser protections are missing. |
| DNS infrastructure | 15/15 | The domain's infrastructure is well hardened. |
Fix priorities
- 1.MediumCSP — protection from script injection · Hardening gap+8
- 2.LowReferrer-Policy · Hardening gap+3
- 3.LowPermissions-Policy · Hardening gap+2
- 4.LowDMARC — anti-spoofing policy · Hardening gap+1
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 9/10An authorized sender list is defined; mail from other servers is flagged as suspicious.
~all (softfail) — acceptable when combined with enforced DMARC. 5 of 10 DNS lookups.
v=spf1 include:_spf.salesforce.com include:_spf.google.com include:amazonses.com include:servers.mcsv.net include:_spf.explore-blue.com ip4:52.212.173.198 ip4:52.212.180.100 ip4:35.156.80.209 ip4:84.88.0.0/28 ip4:84.89.128.88 ip4:62.97.112.196 ip4:149.72.245.97 ~all
$ dig +short TXT upf.edu
DMARC — anti-spoofing policy
Needs attention · Severity: Low · Hardening gap · 14/15Forged email in the company's name is blocked by mail servers.
Policy p=reject. sp=none — subdomains are exposed to spoofing.
v=DMARC1;p=reject;sp=none;rua=mailto:dmarc.informatica@upf.edu
$ dig +short TXT _dmarc.upf.edu
- Keep your current p=reject enforcement and edit the existing record in place — do not replace it with p=none.
- Set sp to match p so subdomains get the same enforcement.
_dmarc.upf.edu. TXT "v=DMARC1; p=reject; sp=reject; rua=mailto:dmarc.informatica@upf.edu"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. Your domain already enforces DMARC. Edit the record in place; never roll back to p=none.
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: google, k1, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCCi1Og52tHwY9beQaRBkX3b56A1zqEVF8d… k1._domainkey: k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i8… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvyWTtNafMsFvGWWnq1rmTOagbks0xNB0… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDieGe8P38pfPjpFu8COFgObuKE2VPI0MabWkZ1…
$ dig +short TXT google._domainkey.upf.edu
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
5 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
1 ASPMX.L.GOOGLE.COM 5 ALT1.ASPMX.L.GOOGLE.COM 5 ALT2.ASPMX.L.GOOGLE.COM 10 ALT3.ASPMX.L.GOOGLE.COM 10 ALT4.ASPMX.L.GOOGLE.COM
$ dig +short MX upf.edu
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://upf.edu/ returned HTTP 200 (final URL: https://www.upf.edu/). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.upf.edu/
$ curl -sIL https://upf.edu/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://upf.edu:443/
HTTP 301 Location: https://upf.edu:443/
$ curl -sI http://upf.edu/ | 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: Amazon Trust Services, expiring 2027-05-30 (192 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: Amazon Trust Services Valid from: 2026-11-13 Valid until: 2027-05-30 Names: *.upf.edu, upf.edu Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect upf.edu:443 -servername upf.edu 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Passed · Severity: OK · 7/8Browsers are told to always use an encrypted connection to the site.
max-age=31536000 (365 days), no includeSubDomains, preload. ≥ 180 days recommended.
Strict-Transport-Security: max-age=31536000; preload
$ curl -sIL https://upf.edu/ | grep -i "Strict-Transport-Security"
CSP — protection from script injection
Failed · Severity: Medium · Hardening gap · 0/8Missing Content-Security-Policy header: this removes one layer of protection against script injection.
No Content-Security-Policy header found.
Content-Security-Policy: (missing)
$ curl -sIL https://upf.edu/ | 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://upf.edu/ | 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://upf.edu/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Failed · Severity: Low · Hardening gap · 0/3Internal URLs (including parameters) may leak to external sites.
Referrer-Policy is missing; the browser will use its default.
Referrer-Policy: (missing)
$ curl -sIL https://upf.edu/ | grep -i "Referrer-Policy"
- Set Referrer-Policy: strict-origin-when-cross-origin.
/* Referrer-Policy: strict-origin-when-cross-origin
Safety: This change is made in your server/CDN settings. Test on staging before production.
Permissions-Policy
Needs attention · Severity: Low · Hardening gap · 0/2Access to sensitive features like the camera and location isn't restricted.
Missing Permissions-Policy header.
Permissions-Policy: (missing)
$ curl -sIL https://upf.edu/ | grep -i "Permissions-Policy"
- Disable browser features the site doesn't need (camera, microphone, geolocation).
/* Permissions-Policy: camera=(), microphone=(), geolocation=()
Safety: This change is made in your server/CDN settings. Test on staging before production. Don't disable a feature the site actually uses.
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://upf.edu/ | 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 upf.edu | grep -E "flags:.* ad"
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 issue "amazonaws.com" | 0 issue "digicert.com" | 0 issue "godaddy.com" | 0 issue "harica.gr" | 0 issue "letsencrypt.org" | 0 issue "pki.goog" | 0 issue "sectigo.com"
0 issue "amazonaws.com" 0 issue "digicert.com" 0 issue "godaddy.com" 0 issue "harica.gr" 0 issue "letsencrypt.org" 0 issue "pki.goog" 0 issue "sectigo.com"
$ dig +short CAA upf.edu
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
4 NS servers.
ns1.upf.edu ns2.upf.edu ns3.upf.edu ns6.upf.edu
$ dig +short NS upf.edu
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 diligence1 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 | upf.edu | 34.36.90.148 |
| AAAA | upf.edu | — |
| MX | upf.edu | 1 ASPMX.L.GOOGLE.COM | 5 ALT1.ASPMX.L.GOOGLE.COM | 5 ALT2.ASPMX.L.GOOGLE.COM | 10 ALT3.ASPMX.L.GOOGLE.COM | 10 ALT4.ASPMX.L.GOOGLE.COM |
| NS | upf.edu | ns1.upf.edu | ns2.upf.edu | ns3.upf.edu | ns6.upf.edu |
| TXT | upf.edu | MS=ms16812314 | nsf8f5p4py69q75j1p3kqxgpz0tjjqm6 | ZOOM_verify_mJj8U21xGOXN3TtDXXeIyV | ca3-18091fbb111f4dc1b7efc926ad2ef9e7 | apple-domain-verification=PFveFCetoRJyrpN4 | MS=2B15116C3E2D6BCD712FE8F458ACB04333FD9B85 | amazonses:SYeYZN1CinJGw33Osdhdjpfil5uFObr3oemjmWpKhk4= | facebook-domain-verification=g1lc5kyqo2hane7oiuxpvsmk3md5kb | v=spf1 include:_spf.salesforce.com include:_spf.google.com include:amazonses.com include:servers.mcsv.net include:_spf.explore-blue.com ip4:52.212.173.198 ip4:52.212.180.100 ip4:35.156.80.209 ip4:84.88.0.0/28 ip4:84.89.128.88 ip4:62.97.112.196 ip4:149.72.245.97 ~all | google-site-verification=izEpPnhlTpzDbmTw8BuKUlcayOcOO_meKumkQJtH_b0 | google-site-verification=kgsCog5ACwbdbHmEZzsbw8ELk06sxYmcgr_XPCInTn4 | google-site-verification=nlwqso-js1jx923vJMJUEYSK4Ht36lf65OEGZl1tgVE | google-site-verification=u6VgmwUxb_pf3OkPUo2ujwats9xWFkXsh7nCxOb41HE | adobe-idp-site-verification=d1f5f1a769e33160ebfdb915440efb7177a613cc5beee99c71fb887f51d6782f | atlassian-domain-verification=iWteD9JmqB0Xxuvyj/ZMat3EaYFeQ/9oen3F5pbSWIvcUYnyYyfxLBzhPV6sOBXf |
| TXT | _dmarc.upf.edu | v=DMARC1;p=reject;sp=none;rua=mailto:dmarc.informatica@upf.edu |
| CAA | upf.edu | 0 issue "amazonaws.com" | 0 issue "digicert.com" | 0 issue "godaddy.com" | 0 issue "harica.gr" | 0 issue "letsencrypt.org" | 0 issue "pki.goog" | 0 issue "sectigo.com" |
| DS | upf.edu | 51307 13 2 b933dd6f2068d1d6b923c8d96e0faa8463e78ea7a9ae4e7eabe06521bd09847a |