Digital exposure report
amsterdamumc.org
Good shape, with a few gaps worth closing this quarter.
Scanned: 2026-11-20 07:30 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://amsterdamumc.org/ | grep -i "Content-Security-Policy"
- 2.
Turn off browser features your site does not use
This limits access to things like camera or location if a page is misused.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://amsterdamumc.org/ | grep -i "Permissions-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- amsterdamumc.org
- Website request
- GET https://amsterdamumc.org/
- Scan time
- 2026-11-20 07:30:30 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 | 30/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 | 19/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.LowPermissions-Policy · Hardening gap+2
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 10/10An authorized sender list is defined and mail from other servers is rejected.
Valid SPF record with -all. 2 of the 10 allowed DNS lookups.
v=spf1 include:spf.protection.outlook.com include:_spf.amsterdamumc.nl -all
$ dig +short TXT amsterdamumc.org
DMARC — anti-spoofing policy
Passed · Severity: OK · 15/15Forged email in the company's name is blocked by mail servers.
Policy p=reject.
v=DMARC1; p=reject; rua=mailto:qij2xmos@ag.eu.dmarcadvisor.com;
$ dig +short TXT _dmarc.amsterdamumc.org
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. Confirm signing with dkim=pass in a sent message's Authentication-Results.
selector1._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwKqyhILz7H4ab6zN0b9A+uYcruGj…
$ dig +short TXT selector1._domainkey.amsterdamumc.org
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 amsterdamumc-org.k-v1.mx.microsoft
$ dig +short MX amsterdamumc.org
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://amsterdamumc.org/ returned HTTP 200 (final URL: https://amsterdamumc.org/). Client-side certificate validation passed.
HTTP 200 Final URL: https://amsterdamumc.org/
$ curl -sIL https://amsterdamumc.org/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 302 → https://amsterdamumc.org/
HTTP 302 Location: https://amsterdamumc.org/
$ curl -sI http://amsterdamumc.org/ | 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: HARICA, expiring 2027-02-23 (95 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: HARICA Valid from: 2026-02-23 Valid until: 2027-02-23 Names: amsterdamumc.nl, amsterdamumc.org, productie.backend.internet-en.amsterdamumc.nl, productie.backend.internet-nl.amsterdamumc.nl, productie.frontend.internet-en-1.amsterdamumc.nl, productie.frontend.internet-en-2.amsterdamumc.nl Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect amsterdamumc.org:443 -servername amsterdamumc.org 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=63072000 (730 days), no includeSubDomains. ≥ 180 days recommended.
Strict-Transport-Security: max-age=63072000
$ curl -sIL https://amsterdamumc.org/ | 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://amsterdamumc.org/ | 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://amsterdamumc.org/ | 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://amsterdamumc.org/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Passed · Severity: OK · 3/3Internal URLs don't leak to external sites.
Referrer-Policy: same-origin
Referrer-Policy: same-origin
$ curl -sIL https://amsterdamumc.org/ | grep -i "Referrer-Policy"
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://amsterdamumc.org/ | 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://amsterdamumc.org/ | 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 amsterdamumc.org | 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 "harica.gr"
0 issue "harica.gr"
$ dig +short CAA amsterdamumc.org
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.zurich.surf.net ns1.surfnet.nl ns2.surfnet.nl ns3.surfnet.nl
$ dig +short NS amsterdamumc.org
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 rulesNo gaps observed
- PCI DSS v4.01 observed gaps
- NIS2 / vendor due diligenceNo gaps observed
- SOC 2 / ISO 27001 baseline1 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 | amsterdamumc.org | 145.117.213.45 |
| AAAA | amsterdamumc.org | — |
| MX | amsterdamumc.org | 0 amsterdamumc-org.k-v1.mx.microsoft |
| NS | amsterdamumc.org | ns1.zurich.surf.net | ns1.surfnet.nl | ns2.surfnet.nl | ns3.surfnet.nl |
| TXT | amsterdamumc.org | MS=ms97292026 | HARICA-2RDX2sCiJ2z6L5topnH | HARICA-wjZYxuVrS1ZsoiO7kyD | google-site-verification=RsSxAB3cDJCN_EXatcWOriyMLwOYcpMS8QLFcDp439s | google-site-verification=dinzuB7hAQIijRYzOL3Gy4tq_TWJEIScVGjh6Mcc18I | v=spf1 include:spf.protection.outlook.com include:_spf.amsterdamumc.nl -all |
| TXT | _dmarc.amsterdamumc.org | v=DMARC1; p=reject; rua=mailto:qij2xmos@ag.eu.dmarcadvisor.com; |
| CAA | amsterdamumc.org | 0 issue "harica.gr" |
| DS | amsterdamumc.org | 303 13 2 1653c2cd9d045abacaa669b41a057840171d42824b77d7ae2315dcdc4cbb9a66 |