Digital exposure report
mhh.de
High exposure. Significant weaknesses put the brand, customers and email at risk.
Scanned: 2026-11-20 07:34 UTC
Partial coverage: the score is based on 95% of applicable check weight. 1 unverified check(s) are excluded, not counted as failures.
What to do first
- 1.
Tell receiving mail servers how to treat fake email from your domain
Without this policy, inboxes have less guidance for spotting messages that impersonate you.
Who can fix it: Your email provider, together with whoever manages your DNS
How to verify after the fix
dig +short TXT _dmarc.mhh.de
- 2.
List the servers allowed to send your email
Without this list, it is easier for others to send email that looks like it came from you.
Who can fix it: Your email provider, together with whoever manages your DNS
How to verify after the fix
dig +short TXT mhh.de
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- mhh.de
- Website request
- GET https://mhh.de/ → https://www.mhh.de/
- Scan time
- 2026-11-20 07:34:36 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- DKIM — digital signature on email · Not detected (common selectors only)
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 | 0/25 | An attacker can send email that looks like it came from the company. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 26/30 | The site instructs browsers to block common attacks. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.HighSPF — who may send mail for the domain · Hardening gap+11
- 2.HighDMARC — anti-spoofing policy · Hardening gap+16
- 3.MediumDNSSEC — signed DNS records · Hardening gap+7
- 4.LowCSP — protection from script injection · Hardening gap+3
To verify
Couldn't be confirmed from public data, so excluded from the score. Checking them clarifies your posture; it doesn't guarantee a score change.
- DKIM — digital signature on email
Findings
SPF — who may send mail for the domain
Failed · Severity: High · Hardening gap · 0/10There is no list of servers authorized to send mail, making it easier to forge email in the company's name.
No v=spf1 TXT record at the domain root. Receiving servers cannot validate the sender's IP address.
(no SPF record found)
$ dig +short TXT mhh.de
- Map every service that sends mail in the domain's name (Google Workspace / Microsoft 365, newsletter tool, CRM).
- Publish exactly one TXT record at the domain root starting with v=spf1.
- Start with ~all, and move to -all once DMARC reports confirm all legitimate senders are covered.
mhh.de. TXT "v=spf1 include:_spf.google.com ~all"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. An incorrect record can block legitimate mail — add every sender before tightening.
DMARC — anti-spoofing policy
Failed · Severity: High · Hardening gap · 0/15No policy tells mail servers to block forged email in the company's name — a common opening for CEO fraud and phishing.
No TXT record at _dmarc.mhh.de. Without DMARC, mail failing SPF/DKIM may still reach the inbox.
(no DMARC record found)
$ dig +short TXT _dmarc.mhh.de
- Step 1 (monitoring, no effect on mail): publish p=none with an rua address to receive reports.
- Step 2: analyze reports for 2–4 weeks and make sure every legitimate sender passes SPF/DKIM.
- Step 3: move to p=quarantine, and finally to p=reject.
_dmarc.mhh.de. TXT "v=DMARC1; p=none; rua=mailto:dmarc@mhh.de; fo=1"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. Jumping straight to reject without a monitoring phase can block legitimate mail.
DKIM — digital signature on email
Not detected (common selectors only) · Severity: OK · Not scoredNo DKIM key was found under the common selectors we probed. That doesn't mean DKIM is missing — selectors can't be listed from public DNS. Not scored.
A missing name for a probed selector (NXDOMAIN/NODATA) only means that selector isn't published. DKIM is marked unverified and excluded from the score. Check a sent message's Authentication-Results for dkim=pass and its s= selector.
Selectors checked: google, selector1, selector2, default, k1, s1, s2, dkim, mail, smtp — no key found google._domainkey: nxdomain selector1._domainkey: nxdomain selector2._domainkey: nxdomain default._domainkey: nxdomain k1._domainkey: nxdomain s1._domainkey: nxdomain s2._domainkey: nxdomain dkim._domainkey: nxdomain mail._domainkey: nxdomain smtp._domainkey: nxdomain
$ dig +short TXT google._domainkey.mhh.de
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
2 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 mx01.ionos.de 10 mx00.ionos.de
$ dig +short MX mhh.de
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://mhh.de/ returned HTTP 200 (final URL: https://www.mhh.de/). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.mhh.de/
$ curl -sIL https://mhh.de/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://mhh.de/
HTTP 301 Location: https://mhh.de/
$ curl -sI http://mhh.de/ | 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-05-11 (172 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-10-24 Valid until: 2027-05-11 Names: betahear.mhh.de, corona.mhh.de, elise.mhh.de, imri.mhh.de, inflame.mhh.de, longcovid.mhh.de Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect mhh.de:443 -servername mhh.de 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://mhh.de/ | grep -i "Strict-Transport-Security"
CSP — protection from script injection
Needs attention · Severity: Low · Hardening gap · 5/8A script policy exists, but it's permissive and offers only partial protection.
script-src includes: 'unsafe-inline', 'unsafe-eval' — weakens XSS protection.
Content-Security-Policy: default-src 'self' https://*.mhh.de chrome-extension; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.mhh.de https://www.probeweis.de https://*.youtube.com https://*.youtube-nocookie.com https://cdnjs.cloudflare.com https://spenden.twingle.de ; script-src-elem 'self' 'unsafe-inline' 'unsafe-eval' https://*.mhh.de https://www.probeweis.de https://*.youtube.com https://*.youtube-nocookie.com https://mh-hannover-390466.workflowcloud.com https://cdnjs.cloudflare.com https://spenden.twingle.de ; script-src-attr 'self' 'unsafe-inline' https://*.mhh.de https://www.probeweis.de; connect-src 'self' https://*.mhh.de https://www.probeweis.de https://*.youtube-nocookie.com https://spenden.twingle.de; style-src 'self' 'unsafe-inline' https://*.mhh.de https://www.probeweis.de; img-src 'self' data: https://*.mhh.de https://www.probeweis.de https://*.ytimg.com ; frame-src 'self' https://*.mhh.de https://www.probeweis.de https://*.youtube-nocookie.com https://mh-hannover-390466.workflowcloud.com https://gbo-app-znc.nintex.io https://spenden.twingle.de; child-src 'self' https://*.mhh.de https://www.probeweis.de https://*.youtube-nocookie.com https://mh-hannover-390466.workflowcloud.com https://gbo-app-znc.nintex.io https://spenden.twingle.de; frame-ancestors 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; report-uri https://www.mhh.de/_mc/csp; report-to https://www.mhh.de/_mc/csp
$ curl -sIL https://mhh.de/ | 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 frame-ancestors 'self'
X-Frame-Options: sameorigin CSP frame-ancestors: 'self'
$ curl -sIL https://mhh.de/ | 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://mhh.de/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Passed · Severity: OK · 3/3Internal URLs don't leak to external sites.
Referrer-Policy: strict-origin-when-cross-origin
Referrer-Policy: strict-origin-when-cross-origin
$ curl -sIL https://mhh.de/ | grep -i "Referrer-Policy"
Permissions-Policy
Passed · Severity: OK · 2/2The site restricts access to sensitive browser features.
Permissions-Policy: camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), usb=()
Permissions-Policy: camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), usb=()
$ curl -sIL https://mhh.de/ | grep -i "Permissions-Policy"
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://mhh.de/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Needs attention · Severity: Medium · Hardening gap · 0/7The domain's records aren't signed, so in some scenarios users could be redirected to a forged server.
No DS record is published at the parent zone, so there's no DNSSEC chain of trust for this zone.
AD = false DS mhh.de: NODATA
$ dig +short DS mhh.de
- Enable DNSSEC at your DNS provider (one click at most providers).
- Copy the DS record your provider generates to your domain registrar.
- Wait for propagation and verify with DNSViz.
dig +dnssec mhh.de SOA delv mhh.de
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. A wrong DS record at the registrar will make the domain stop resolving — copy it exactly from the provider.
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 issue "pki.dfn.de" | 0 issue "harica.gr"
0 issue "pki.dfn.de" 0 issue "harica.gr"
$ dig +short CAA mhh.de
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
2 NS servers.
nsext2.mh-hannover.de nsext1.mh-hannover.de
$ dig +short NS mhh.de
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 rules2 observed gaps · 1 unverified
- PCI DSS v4.01 observed gaps
- NIS2 / vendor due diligence3 observed gaps
- SOC 2 / ISO 27001 baseline3 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 | mhh.de | 193.174.105.70 |
| AAAA | mhh.de | — |
| MX | mhh.de | 10 mx01.ionos.de | 10 mx00.ionos.de |
| NS | mhh.de | nsext2.mh-hannover.de | nsext1.mh-hannover.de |
| TXT | mhh.de | — |
| TXT | _dmarc.mhh.de | — |
| CAA | mhh.de | 0 issue "pki.dfn.de" | 0 issue "harica.gr" |
| DS | mhh.de | — |