DNS Gurus
Cached · just now
77/100 SECURITY SCORE

Certificate Information

Subject
CN=*.geckoform.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M02
Valid From
February 28, 2025
Valid Until
March 29, 2026 59 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
68:D7:87:33:64:6A:6B:45:42:BD:90:30:9D:CF:33:A2:6B:42:EA:71:12:6B:A9:70:E1:A4:84:EB:D7:D3:61:BE
Alternative Names
6 domains

Security Configuration

TLS Protocols
TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)

HTTP Security Headers

Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Present
ch-ua=("*"), ch-ua-mobile=("*"), ch-ua-platform=("*"), ch-ua-platform-version=("*"), ch-ua-arch=("*"), ch-ua-bitness=("*"), ch-ua-full-version-list=("*")
Recommendations
  • • Add Strict-Transport-Security header with max-age of at least 1 year
  • • Add Content-Security-Policy header to prevent XSS attacks
  • • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • Add X-Content-Type-Options: nosniff
  • • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)

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

6 domains
gecko.fm *.gecko.fm

Other domains in certificate

geckochat.io *.geckochat.io
geckoform.com *.geckoform.com