Open
Cached
·
just now
95/100
SECURITY SCORE
Certificate Information
Subject
CN=web.app
Issuer
C=US, O=Google Trust Services, CN=WR4
Valid From
January 05, 2026
Valid Until
April 05, 2026
75 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
82:B4:DD:07:D6:47:86:3A:C9:76:59:97:94:F8:7D:22:47:B4:01:4F:0B:66:5E:12:21:9C:AD:0D:78:9F:DB:BA
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
Excellent
max-age=31556926; includeSubDomains; preload
Content-Security-Policy
Good
default-src; script-src; style-src; +4 more
default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://www.google-analytics.com https://connect.facebook.net; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' https://coretech-egypt.com https://images.unsplash.com data: blob:; connect-src 'self' https://www.google-analytics.com https://www.googletagmanager.com https://connect.facebook.net; frame-src 'self' https://www.google.com;
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
origin-when-cross-origin
Permissions-Policy
Present
camera=(), microphone=(), geolocation=()
Recommendations
- • Strengthen CSP by removing 'unsafe-eval'
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