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:
Unknown Certificate Authority - the server's certificate is not trusted
Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
PayPal
YouTube
Adyen
Arkose Labs
Amazon S3
Brightcove
Active incidents
Cloudinary
DocuSign
Embedly
Active incidents
Forethought
GoDaddy
Google Analytics
Google DoubleClick
Google Pay
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
LinkedIn
Salesforce Cloud
Salesforce Sites
Stripe
Vidyard
Vimeo
Wistia
Google Cloud
Certificate Information
Subject
CN=support.artera.io
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
November 07, 2025
Valid Until
December 09, 2026
211 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
ED:D8:8F:2E:95:AC:83:DA:9D:6E:88:BC:63:4A:4C:BF:24:82:69:CC:38:3B:82:89:13:DE:D0:E5:A4:D0:14:B2
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=63072000; includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Significantly strengthen CSP directives
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • Consider adding Permissions-Policy to control browser features
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