Open
Cached
·
just now
91/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=shippypro.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 08, 2026
Valid Until
July 07, 2026
68 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
B7:6A:70:DB:E9:49:02:35:B3:1D:B1:84:B7:18:E1:00:FF:0F:7D:18:98:05:83:3F:3F:F2:7F:33:D6:36:41:12
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
Good
max-age=31536000; includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
accelerometer=(), autoplay=(), camera=(); +5 more
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Significantly strengthen CSP directives
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
Subject Alternative Names
20 domains
shippypro.com
*.shippypro.com
blog.shippypro.com
cdn.shippypro.com
demo.shippypro.com
get.shippypro.com
help.shippypro.com
maps.shippypro.com
returns.shippypro.com
status.shippypro.com
ws.shippypro.com
*.blog.shippypro.com
*.cdn.shippypro.com
*.demo.shippypro.com
*.get.shippypro.com
*.help.shippypro.com
*.maps.shippypro.com
*.returns.shippypro.com
*.status.shippypro.com
*.ws.shippypro.com