tierpark-berlin.de security report

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

52risk

Elevated

Several issues worth triaging this week.

0Critical

1High

3Medium

4Low

2Info

Collected 16 hours ago9.5sfrom cache

Certificate Transparency
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs8
Registration
DNS posture4
Email authentication1
Certificate
Security headers1
Archived URLs
Analysis10

noteCertificate Transparency did not complete (HTTP 502). Results below are partial.
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.
noteNo registration data: RDAP has no record at this level.

SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.tierpark-berlin.de TXT "v=DMARC1; p=none; rua=mailto:dmarc@tierpark-berlin.de"`, review the reports, then move to p=quarantine and p=reject.
asset: tierpark-berlin.de
Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://www.tierpark-berlin.de/de
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.tierpark-berlin.de/de
No X-Frame-Options or CSP frame-ancestors directive, so another site can load this page invisibly inside its own and trick users into clicking.
What to do
Send `X-Frame-Options: DENY` or `Content-Security-Policy: frame-ancestors ’none’`.
asset: https://www.tierpark-berlin.de/de
5.57.42.105 (tierpark-berlin.de) reports openresty 1.31.1.1. 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: 5.57.42.105
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.tierpark-berlin.de/de
Exact versions in response headers let anyone match the server against a CVE feed without touching it.
What to do
Strip version tokens (`ServerTokens Prod`, `server_tokens off`, remove X-Powered-By).
asset: https://www.tierpark-berlin.de/de
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: tierpark-berlin.de
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: tierpark-berlin.de
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: tierpark-berlin.de

final https://www.tierpark-berlin.de/destatus 200time 4318msstack cloudflare · PHP/7.4.33 · TYPO3 CMS

✓http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✗Clickjacking protection
✓X-Content-Type-Options
nosniff
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 4 servers
mx01.hornetsecurity.com mx02.hornetsecurity.com mx03.hornetsecurity.com mx04.hornetsecurity.com
✓SPFends in -all
v=spf1 mx ip4:178.238.225.75/32 ip4:85.10.194.60/32 ip4:5.57.42.105/32 ip4:185.199.104.0/22 include:spf.mailjet.com include:spf.protection.outlook.com include:spf.eu.exclaimer.net include:spf.hornetsecurity.com include:spf.codepiraten.com -all
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
nsa0.schlundtech.de nsb0.schlundtech.de nsc0.schlundtech.de nsd0.schlundtech.de

Address	Ports	CVEs	Edge	Network
5.57.42.105 tierpark-berlin.de +25	80443208220832086208720952096	0	direct	—

Archived URLs

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

tierpark-berlin.de security report

Elevated

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames