Open
Cached
·
just now
85/100
SECURITY SCORE
Detected Technologies
AWS API Gateway
Plyr
Akamai
Active incidents
Amplitude
AWS
Active incidents
GitHub
GoDaddy
Google Analytics
Google API JS Client
Google Cloud Functions
Google Cloud Storage
Google DoubleClick
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
jsDelivr
LinkedIn
Microsoft Clarity
Vimeo
Google Cloud
Certificate Information
Subject
CN=*.webfg.com
Issuer
C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., OU=http://certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2
Valid From
June 09, 2026
Valid Until
December 24, 2026
129 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
59:02:56:24:47:14:74:D9:4B:AC:17:42:9F:B1:BE:0E:52:7E:E8:43:82:2E:39:71:A4:09:15:03:39:8B:83:24
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=63072000; includeSubdomains; preload
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
geolocation=(self), microphone=(), camera=(); +1 more
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
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