Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
pornid.xxx scored 65/100, meeting baseline requirements but with 9 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: Security Headers. Positive signals: MX Records & Mail Provider, Known Breaches, HSTS Header 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 pornid.xxx compares
Grade distribution across 2598 companies we've scanned. pornid.xxx scores better than 34% of them.
83
A+
25
A
190
A-
196
B+
75
B
362
B-
129
C+
114
C
330
C-
119
D+
95
D
252
D-
628
F
pornid.xxx — Grade D (65/100)
2598 companies scanned
Security checks
Each check inspects a different part of pornid.xxx's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
1/5 security headers present. Missing: CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
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 (chin.ns.cloudflare.com., hugh.ns.cloudflare.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
DMARC / Email Security
Strengths: DKIM configured (selectors: mail). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua); SPF record uses neutral (?all) — no real enforcement.
TLS Protocol Support
Strengths: TLS 1.2 supported; TLS 1.2 supported (consider enabling TLS 1.3). Protocol support: TLS 1.3: No, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
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.
Cookie Security
Strengths: 2 cookie(s) analyzed; All cookies have Secure flag; All cookies have SameSite attribute. Issues: 2/2 cookie(s) missing HttpOnly flag (PHPSESSID, kt_ips).
Certificate Hygiene
Strengths: Certificate valid, 209 days remaining; Issued by Sectigo Limited; 180 certificates logged in CT. Issues: Certificates issued by 6 different CAs (threshold: 5 for 180 logged certs) — possible misconfiguration or shadow IT. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
MX Records & Mail Provider
Strengths: Mail handled by mail.pornid.xxx; 2 MX record(s) configured; Multiple MX records provide redundancy.
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=63072000s (730 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
CVE Exposure
Detected technologies: nginx. No version information exposed — CVE matching not possible (this is good practice).
Recommended actions
5 items
Steps to improve pornid.xxx's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for pornid.xxx 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.pornid.xxx
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, Referrer-Policy, Permissions-Policy)
4 of 5 recommended security headers are missing on pornid.xxx: CSP, X-Content-Type-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: Referrer-Policy: strict-origin-when-cross-origin
4
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
5
Verify with: curl -sI https://pornid.xxx | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for pornid.xxx 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 .xxx TLD
4
Verify: dig +dnssec pornid.xxx
4
Upgrade to TLS 1.3
pornid.xxx negotiated TLSv1.2. TLS 1.2 is still compliant under all major security frameworks and is not a vulnerability. TLS 1.3 offers faster handshakes and removes legacy cipher negotiation. This is a best-practice improvement, not a compliance gap.
How to fix this
1
Update web server config to prefer TLS 1.3 (nginx: ssl_protocols TLSv1.2 TLSv1.3)
2
Verify: openssl s_client -connect pornid.xxx:443 -tls1_3
5
Review certificate configuration
Certificate issues found for pornid.xxx: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. These are operational hygiene items, not immediate security risks.
How to fix this
1
Consider replacing wildcard cert with individual certs for critical subdomains
2
Consolidate certificate issuance to 1–2 trusted CAs
At a glance
Key data points from the scan.
TLS Version
TLSv1.2
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DMARC Policy
p=none
Strengths: DKIM configured (selectors: mail). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua); SPF record uses neutral (?all) — no real enforcement.
SPF Record
Present
v=spf1 a mx include:_spf.smtp.advancedhosters.com ?all
Security Headers
1/5 present
Missing: CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=63072000s (730 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
SSL Certificate
Issues
Strengths: Certificate valid, 209 days remaining; Issued by Sectigo Limited; 180 certificates logged in CT. Issues: Certificates issued by 6 different CAs (threshold: 5 for 180 logged certs) — possible misconfiguration or shadow IT. 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 (chin.ns.cloudflare.com., hugh.ns.cloudflare.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.