spie.de security report

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

32risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

1High

0Medium

16Low

2Info

Collected 19 hours ago3.3sfrom cache

Certificate Transparency78
DNS resolution18
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs10
Registration
DNS posture5
Email authentication1
Certificate
Security headers5
Archived URLs
Analysis19

noteFound 78 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteFound 13 addresses; enriching the first 12.
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.spie.de TXT "v=DMARC1; p=none; rua=mailto:dmarc@spie.de"`, review the reports, then move to p=quarantine and p=reject.
asset: spie.de
129.185.166.144 (test.safetyapp.spie.de) reports nginx 1.28.0. 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: 129.185.166.144
domino-dpf-admin.spie.de 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: domino-dpf-admin.spie.de
vpn-ffm.spie.de 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: vpn-ffm.spie.de
qa.spie.de 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: qa.spie.de
dev.aiwa.spie.de 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: dev.aiwa.spie.de
dev.cvat.spie.de 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: dev.cvat.spie.de
test.aiwa.spie.de 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: test.aiwa.spie.de
athena-dev.spie.de 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: athena-dev.spie.de
www.dev.cvat.spie.de 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: www.dev.cvat.spie.de
fiori-test-erp.spie.de 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: fiori-test-erp.spie.de
test.safetyapp.spie.de 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: test.safetyapp.spie.de
classifier-test.spie.de 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: classifier-test.spie.de
dev-ef-contactapp.spie.de 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: dev-ef-contactapp.spie.de
athena-dev-backend.spie.de 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: athena-dev-backend.spie.de
test.support-cegit.spie.de 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: test.support-cegit.spie.de
www.test.safetyapp.spie.de 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: www.test.safetyapp.spie.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: spie.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: spie.de

final https://spie.de/status 200time 1482msstack cloudflare · ASP.NET · Sitefinity 15.4.8631.0 DX

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=31536000; includeSubDomains
✓Content-Security-Policy
default-src 'self' *.googleapis.com https://s.ytimg.com *.ytimg.com *.youtube.com spie-web.azurewebsites.net http://spie-web.azurewebsites.net spie-web-preprod.…
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
no-referrer-when-downgrade
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Cookie ARRAffinity
Secure · HttpOnly · no SameSite
✓Cookie ARRAffinitySameSite
Secure · HttpOnly · SameSite=none

✓Receives mail via 2 servers
mxa-0053e201.gslb.pphosted.com mxb-0053e201.gslb.pphosted.com
✓SPFends in -all
v=spf1 include:spf.protection.outlook.com ip4:47.189.54.97 ip4:47.189.54.117 ip4:217.195.17.68 include:spf-0053e201.pphosted.com -all
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

✓DNSSECanswers are signed and validated
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓5 nameservers
nsa.perf1.fr nsb.perf1.com nsc.perf1.com nsz.perf1.com nsz.perf1.fr

Address	Ports	Edge	Network
52.166.119.99 spie.de +3	80443	direct	—
150.171.110.102 qa.spie.de +3	80443	direct	—
98.71.191.240 dev.cvat.spie.de	80443	direct	—
185.60.36.20 webmail.spie.de +3	80443	direct	—
185.60.36.11 citrix-dze.spie.de +1	80	direct	—
129.185.166.144 test.safetyapp.spie.de +2	443	direct	—
46.189.54.80 vpn-ffm.spie.de	none known	direct	—
20.71.174.38 athena-dev.spie.de +1	none known	direct	—
185.60.39.112 fiori-test-erp.spie.de	none known	direct	—
129.185.166.148 classifier-test.spie.de	none known	direct	—
129.185.166.151 test.support-cegit.spie.de	none known	direct	—
185.60.39.116 mail.spie.de	none known	direct	—

Archived URLs

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

spie.de security report

Moderate

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames