Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
serverhunter.com scored 95/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: MX Records & Mail Provider, TLS Configuration, DNS Configuration all passed.
1 action item identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How serverhunter.com compares
Grade distribution across 2445 companies we've scanned. serverhunter.com scores better than 96% of them.
75
A+
24
A
180
A-
187
B+
71
B
342
B-
118
C+
112
C
308
C-
114
D+
93
D
226
D-
595
F
serverhunter.com — Grade A (95/100)
2445 companies scanned
Security checks
Each check inspects a different part of serverhunter.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.
DNS CAA Records
Strengths: CAA records configured (10 record(s)); Authorized CAs: letsencrypt.org, pki.goog; cansignhttpexchanges=yes, ssl.com, comodoca.com, digicert.com; cansignhttpexchanges=yes. Issues: No iodef record — CA violations won't be reported to the domain owner.
Security Headers
3/5 security headers present. Missing: Referrer-Policy, Permissions-Policy.
security.txt (RFC 9116)
No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.
MX Records & Mail Provider
Strengths: Mail handled by linda.mx.cloudflare.net; 3 MX record(s) configured; Multiple MX records provide redundancy.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DNS Configuration
Strengths: 2 nameservers configured (anna.ns.cloudflare.com., terry.ns.cloudflare.com.); 3 MX records present; DNSSEC enabled; Zone transfers properly restricted.
TLS Protocol Support
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
HSTS Header
HSTS enabled: max-age=31536000s (365 days) with includeSubDomains and preload. Meets best-practice configuration.
Known Breaches
No known breaches found in public disclosure databases.
Cookie Security
No cookies set on the homepage response. No cookie security flags to evaluate.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google).
CVE Exposure
Detected technologies: cloudflare. (cloudflare detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Certificate Hygiene
Strengths: Certificate valid, 87 days remaining; Issued by Google Trust Services; 649 certificates logged in CT; Certificates from 6 CAs: "CloudFlare, "Cloudflare, COMODO CA Limited. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
Recommended actions
1 item
Steps to improve serverhunter.com's security grade, ranked by impact.
1
Add optional security headers (Referrer-Policy, Permissions-Policy)
serverhunter.com has most security headers configured. Missing: Referrer-Policy, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add: Referrer-Policy: strict-origin-when-cross-origin
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://serverhunter.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google).
SPF Record
Present
v=spf1 include:_spf.google.com include:amazonses.com include:_spf.mx.cloudflare.net -all
Security Headers
3/5 present
Missing: Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000s (365 days) with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 87 days remaining; Issued by Google Trust Services; 649 certificates logged in CT; Certificates from 6 CAs: "CloudFlare, "Cloudflare, COMODO CA Limited. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
DNSSEC
Enabled
Strengths: 2 nameservers configured (anna.ns.cloudflare.com., terry.ns.cloudflare.com.); 3 MX records present; DNSSEC enabled; Zone transfers properly restricted.