Open
Cached
·
just now
82/100
SECURITY SCORE
Detected Technologies
Adobe Audience Manager
Amplitude
AWS
AWS Certificate Manager
Amazon S3
Brightcove
Cloudflare CDNJS
Datadog
Facebook
Google Analytics
Google API JS Client
Google DoubleClick
Google Fonts
Google Optimize
Google Search
Google Sign-In
Google Tag Manager
Heap
Hotjar
Maze
Megaphone
Pinterest
Qualtrics
Segment
Snapchat
Taboola
Tealium
Twitter
YouTube
Certificate Information
Subject
CN=seek.com.au
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
October 14, 2025
Valid Until
November 12, 2026
194 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
B8:F6:04:8A:0E:E9:A4:88:46:47:98:CC:50:7D:32:C4:C8:54:26:54:75:E6:77:93:FB:50:91:8C:41:02:8B:CA
Alternative Names
Security Configuration
TLS Protocols
TLS 1.0
TLS 1.1
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
- • TLS 1.1 is deprecated and should be disabled
- • TLS 1.0 is deprecated and should be disabled
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=157680000
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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