SSL Verification Bypassed
The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.
Reason:
Hostname Mismatch - certificate is issued for *.brickftp.com, *.exavault.com, *.files.com, *.ftphosting.net, *.smartfile.com, brickftp.com, exavault.com, files.com, ftphosting.net, not for ec2-34-204-153-236.compute-1.amazonaws.com
Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=files.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
December 01, 2025
Valid Until
March 01, 2026
88 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F3:4E:2B:09:D0:DF:58:63:2F:06:E8:CE:A1:2A:47:BD:89:11:17:FF:47:39:22:2F:10:99:33:C6:9E:F4:EA:A2
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=631139040; includeSubdomains; preload;
Content-Security-Policy
Basic
base-uri; block-all-mixed-content; child-src; +12 more
base-uri 'self'; block-all-mixed-content ; child-src brickftp.com go.oncehub.com 'self'; connect-src 'self' *.files.com *.s3.amazonaws.com s3.amazonaws.com s3-af-south-1.amazonaws.com s3-ap-northeast-1.amazonaws.com s3-ap-northeast-2.amazonaws.com s3-ap-northeast-3.amazonaws.com s3-ap-south-1.amazonaws.com s3-ap-southeast-1.amazonaws.com s3-ap-southeast-2.amazonaws.com s3-ca-central-1.amazonaws.com s3-eu-central-1.amazonaws.com s3-eu-north-1.amazonaws.com s3-eu-south-1.amazonaws.com s3-eu-west-1.amazonaws.com s3-eu-west-2.amazonaws.com s3-eu-west-3.amazonaws.com s3-me-south-1.amazonaws.com s3-sa-east-1.amazonaws.com s3-us-east-1.amazonaws.com s3-us-east-2.amazonaws.com s3-us-gov-east-1.amazonaws.com s3-us-gov-west-1.amazonaws.com s3-us-west-1.amazonaws.com s3-us-west-2.amazonaws.com; font-src 'self' data:; form-action 'self'; frame-src 'self' go.oncehub.com wopi.files.com wopi1.files.com wopi2.files.com jssdk.files.com; img-src 'self' data: blob: https:; media-src 'self' *.amazonaws.com *.wasabisys.com *.files.com; object-src 'self'; script-src 'self' 'nonce-hpriuFQ6jcA1I1dkDgeyLaGTPqF3lNIA'; script-src-elem 'self'; style-src 'self' 'unsafe-inline'; upgrade-insecure-requests ; worker-src 'self'
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
geolocation=(), midi=(), sync-xhr=(), microphone=(), camera=(), magnetometer=(), gyroscope=(), fullscreen=(self), payment=()
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
CAA Records (Certificate Authority Authorization)
CAA Records
Not Configured
(Any CA can issue certificates)
CAA Issues
- • No CAA records configured - any CA can issue certificates
Recommendations
- • Implement CAA records to restrict which CAs can issue certificates for your domain
- • This adds an extra layer of security against unauthorized certificate issuance
- • Example: Add CAA record 'example.com. CAA 0 issue "letsencrypt.org"'
- • Consider adding 'iodef' record to receive security incident reports