rdgg.nl security report

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

34risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

2Medium

12Low

2Info

Collected 8 hours ago23.4sfrom cache

Certificate Transparency133
DNS resolution8
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs12
Registration
DNS posture2
Email authentication2
Certificate
Security headers4
Archived URLs
Analysis16

noteFound 133 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.

Receivers are asked to report spoofing but not to block it. This is the right first step, and the wrong place to stop.
What to do
Once reports look clean, move to p=quarantine, then p=reject.
asset: rdgg.nl
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: rdgg.nl
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 84.241.159.91:25
84.241.159.94 (webmail.rdgg.nl) reports internet information services 10.0, outlook web access 15.2.2562.46. 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: 84.241.159.94
84.241.159.92 (oos.rdgg.nl) reports internet information services 10.0, 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: 84.241.159.92
zorgplatform-test.rdgg.nl 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: zorgplatform-test.rdgg.nl
staging.reiniercampus.rdgg.nl 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: staging.reiniercampus.rdgg.nl
legacy.rdgg.nl 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: legacy.rdgg.nl
mijn-intranet.rdgg.nl 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: mijn-intranet.rdgg.nl
acc-mijn-intranet.rdgg.nl 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: acc-mijn-intranet.rdgg.nl
accept-mijn-intranet.rdgg.nl 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: accept-mijn-intranet.rdgg.nl
preprod-mijn-intranet.rdgg.nl 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: preprod-mijn-intranet.rdgg.nl
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://reinierdegraaf.nl/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://reinierdegraaf.nl/
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: rdgg.nl
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: rdgg.nl

final https://reinierdegraaf.nl/status 200time 2114msstack cloudflare

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=31536000; includeSubDomains
✓Content-Security-Policy
base-uri 'self';connect-src 'self' https://*.google-analytics.com https://*.doubleclick.net;default-src 'self';font-src 'self' https://use.typekit.net https://f…
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

!Cookie XSRF-TOKEN
Secure · no HttpOnly · SameSite=lax
✓Cookie rdgg_session
Secure · HttpOnly · SameSite=lax

✓Receives mail via 1 server
mail10.rdgg.nl
✓SPFends in -all
v=spf1 mx include:_spf.zorgmail.nl include:spf.protection.outlook.com -all
!DMARCp=none
v=DMARC1; p=none; rua=mailto:ytdouhhi@ag.eu.dmarcadvisor.com;
!MTA-STSinbound mail can be downgraded to plaintext

✓DNSSECanswers are signed and validated
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
ns.eatserver.nl ns2.eatserver.nl

✓Registered with Registrar.eu29.6 years old
rdgg.nl
–Registration expiry
✗Transfer lock
none
✓2 nameservers at registry
ns.eatserver.nl ns2.eatserver.nl

Address	Ports	Edge	Network
84.241.159.91 smtp.rdgg.nl +3	25443465587	direct	—
18.159.223.183 rdgg.nl +2	80443	direct	—
185.173.22.22 staging.reiniercampus.rdgg.nl +3	80443	direct	—
84.241.159.94 webmail.rdgg.nl +8	80443	direct	—
95.128.94.31 login.rdgg.nl +4	443	direct	—
84.241.159.92 oos.rdgg.nl +8	443	direct	—
95.128.94.2 sslvpn.rdgg.nl	none known	direct	—

Archived URLs

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

rdgg.nl security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames