Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
metin2.vote scored 62/100, meeting baseline requirements but with 6 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: HSTS Header, Security Headers, Cookie Security. Positive signals: MX Records & Mail Provider, TLS Protocol Support, TLS Configuration all passed.
5 action items 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 metin2.vote compares
Grade distribution across 2445 companies we've scanned. metin2.vote scores better than 25% 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
metin2.vote — Grade D- (62/100)
2445 companies scanned
Security checks
Each check inspects a different part of metin2.vote's public security setup. Green means healthy, yellow needs attention, red is a problem.
HSTS Header
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
Security Headers
None of the 5 recommended security headers are present (missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy). This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
Cookie Security
Strengths: 1 cookie(s) analyzed; All cookies have Secure flag. Issues: 1/1 cookie(s) missing HttpOnly flag (PHPSESSID); 1/1 cookie(s) missing SameSite attribute (PHPSESSID).
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
No CAA records found. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorized CAs only, reducing the risk of misissued certificates.
DNS Configuration
Strengths: 2 nameservers configured (dion.ns.cloudflare.com., celeste.ns.cloudflare.com.); 3 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: default). Issues: No DMARC record found — email spoofing is not prevented.
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.
CVE Exposure
Detected technologies: cloudflare, PHP/8.2.30, metin2.vote. (cloudflare detected but excluded from CVE matching — upstream infrastructure). 2 high-severity CVE(s) found (CVSS 7.0–8.9): CVE-2025-14177, CVE-2025-14180. Patching recommended.
MX Records & Mail Provider
Strengths: Mail handled by mx1-hosting.jellyfish.systems; 3 MX record(s) configured; Multiple MX records provide redundancy.
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.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Known Breaches
No known breaches found in public disclosure databases.
Certificate Hygiene
Strengths: Certificate valid, 74 days remaining; Issued by Google Trust Services. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
Recommended actions
5 items
Steps to improve metin2.vote's security grade, ranked by impact.
1
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on metin2.vote. Without it, connections can be downgraded from HTTPS to HTTP via man-in-the-middle attacks. This is a straightforward server configuration change.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Required application security controls
NIST 800-53SC-8
Transmission confidentiality and integrity
How to fix this
1
Add header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify all subdomains support HTTPS before adding includeSubDomains
3
Test with: curl -sI https://metin2.vote | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Add missing security headers (CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy)
5 of 5 recommended security headers are missing on metin2.vote: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy. These headers protect against clickjacking, MIME-sniffing, and unauthorized browser feature access. Adding them is a server configuration change with no application code changes required.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Security headers are required application controls
OWASPSecure Headers
Recommended baseline for web applications
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: X-Content-Type-Options: nosniff
3
Add: X-Frame-Options: SAMEORIGIN (use DENY only if you never embed your pages in iframes)
4
Add: Referrer-Policy: strict-origin-when-cross-origin
5
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
6
Verify with: curl -sI https://metin2.vote | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Strengthen email authentication configuration
Email authentication is partially configured for metin2.vote but has gaps. Actions needed: upgrade DMARC policy from 'none' to 'quarantine' or 'reject'. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
How to fix this
1
Upgrade DMARC policy to p=quarantine (then p=reject after monitoring)
2
Verify with: nslookup -type=txt _dmarc.metin2.vote
4
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for metin2.vote can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.
Compliance impact
NIST 800-53SC-20
Secure name/address resolution service
How to fix this
1
Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2
Enable DNSSEC signing in your DNS provider dashboard
3
Add the DS record to your registrar for .vote TLD
4
Verify: dig +dnssec metin2.vote
5
Review potential CVE exposure in detected software
Software detected on metin2.vote has potential CVE matches. Review the specific CVEs and confirm whether the installed version is affected.
How to fix this
1
Review matched CVEs and confirm installed versions
2
Update software if vulnerable versions are confirmed
3
Consider hiding version information in server headers
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
Not configured
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: default). Issues: No DMARC record found — email spoofing is not prevented.
SPF Record
Present
v=spf1 +mx +a +ip4:198.54.120.111 +include:spf.web-hosting.com ~all
Security Headers
0/5 present
Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Not enabled
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
SSL Certificate
Valid
Strengths: Certificate valid, 74 days remaining; Issued by Google Trust Services. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (dion.ns.cloudflare.com., celeste.ns.cloudflare.com.); 3 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.