Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
androidfilehost.com scored 68/100, meeting baseline requirements but with 7 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: Security Headers, Cookie Security. Positive signals: MX Records & Mail Provider, TLS Configuration, TLS Protocol Support 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 androidfilehost.com compares
Grade distribution across 2436 companies we've scanned. androidfilehost.com scores better than 37% of them.
75
A+
24
A
183
A-
186
B+
70
B
342
B-
117
C+
111
C
307
C-
113
D+
93
D
220
D-
595
F
androidfilehost.com — Grade D+ (68/100)
2436 companies scanned
Security checks
Each check inspects a different part of androidfilehost.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
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. Issues: 1/1 cookie(s) missing Secure flag (afh); 1/1 cookie(s) missing HttpOnly flag (afh); 1/1 cookie(s) missing SameSite attribute (afh).
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 (12 record(s)); Authorized CAs: digicert.com; cansignhttpexchanges=yes, globalsign.com, letsencrypt.org, pki.goog; cansignhttpexchanges=yes, ssl.com, comodoca.com. Issues: No iodef record — CA violations won't be reported to the domain owner.
DNS Configuration
Strengths: 2 nameservers configured (kara.ns.cloudflare.com., seth.ns.cloudflare.com.); 5 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: google, s1, s2, mail, zendesk1, zendesk2). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
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.
HSTS Header
HSTS configured but max-age=0s (0 days) is extremely low. Browsers will not cache this policy meaningfully. Increase to at least 15552000s (180 days).
CVE Exposure
Detected technologies: cloudflare, PHP/7.4.5. (cloudflare detected but excluded from CVE matching — upstream infrastructure). 2 high-severity CVE(s) found (CVSS 7.0–8.9): CVE-2022-31090, CVE-2022-31091. Patching recommended.
MX Records & Mail Provider
Strengths: Mail handled by Google Workspace; 5 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.
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.
Certificate Hygiene
Strengths: Certificate valid, 47 days remaining; Issued by Let's Encrypt. 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 androidfilehost.com's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for androidfilehost.com 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.androidfilehost.com
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 androidfilehost.com: 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://androidfilehost.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for androidfilehost.com 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 .com TLD
4
Verify: dig +dnssec androidfilehost.com
4
Increase HSTS max-age duration
HSTS is enabled but the max-age (0s) is below the recommended minimum of 15768000s (6 months). A short max-age means browsers forget the HTTPS-only policy quickly, reducing protection between visits.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Application security header configuration
How to fix this
1
Update header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify: curl -sI https://androidfilehost.com | grep -i strict
5
Review potential CVE exposure in detected software
Software detected on androidfilehost.com 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
p=none
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2, mail, zendesk1, zendesk2). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
SPF Record
Present
v=spf1 mx include:aspmx.googlemail.com include:_spf.google.com include:mailgun.org include:amazonses
Security Headers
0/5 present
Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Not enabled
HSTS configured but max-age=0s (0 days) is extremely low. Browsers will not cache this policy meaningfully. Increase to at least 15552000s (180 days).
SSL Certificate
Valid
Strengths: Certificate valid, 47 days remaining; Issued by Let's Encrypt. 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 (kara.ns.cloudflare.com., seth.ns.cloudflare.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.