Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
arena-top100.com scored 95/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: DNS Configuration, TLS Configuration, TLS Protocol Support 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 arena-top100.com compares
Grade distribution across 2445 companies we've scanned. arena-top100.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
arena-top100.com — Grade A (95/100)
2445 companies scanned
Security checks
Each check inspects a different part of arena-top100.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.
MX Records & Mail Provider
Strengths: Mail handled by mail.arena-top100.com; 1 MX record(s) configured. Issues: Only 1 MX record — no failover if primary mail server is unavailable.
DNS CAA Records
Strengths: CAA records configured (10 record(s)); Authorized CAs: comodoca.com, digicert.com; cansignhttpexchanges=yes, letsencrypt.org, pki.goog; cansignhttpexchanges=yes, ssl.com. Issues: No iodef record — CA violations won't be reported to the domain owner.
Security Headers
3/5 security headers present. Missing: CSP, 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.
DNS Configuration
Strengths: 2 nameservers configured (justin.ns.cloudflare.com., roxy.ns.cloudflare.com.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
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.
Known Breaches
No known breaches found in public disclosure databases.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all); DKIM configured (selectors: default).
HSTS Header
HSTS enabled: max-age=15552000s (180 days). includeSubDomains present. preload present.
Cookie Security
No cookies set on the homepage response. No cookie security flags to evaluate.
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, 66 days remaining; Issued by Google Trust Services; 405 certificates logged in CT; Certificates from 7 CAs: "CloudFlare, "Cloudflare, "cPanel. 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 arena-top100.com's security grade, ranked by impact.
1
Add optional security headers (CSP, Permissions-Policy)
arena-top100.com has most security headers configured. Missing: CSP, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add a Content-Security-Policy header. Safe starting value (works with Google Fonts and inline styles/scripts): default-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; script-src 'self' 'unsafe-inline'; upgrade-insecure-requests. Test your site after adding it, then tighten over time by removing 'unsafe-inline'.
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://arena-top100.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 soft-fail (~all); DKIM configured (selectors: default).
SPF Record
Present
v=spf1 +mx +a +ip4:15.204.249.165 ~all
Security Headers
3/5 present
Missing: CSP, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=15552000s (180 days). includeSubDomains present. preload present.
SSL Certificate
Valid
Strengths: Certificate valid, 66 days remaining; Issued by Google Trust Services; 405 certificates logged in CT; Certificates from 7 CAs: "CloudFlare, "Cloudflare, "cPanel. 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 (justin.ns.cloudflare.com., roxy.ns.cloudflare.com.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.