B
85/100

jobstreet.com

May 14, 2026 ·
6 Warnings 8 Passed 14 checks
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks; sending servers cannot verify your mail server requires TLS; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks; sending servers cannot verify your mail server requires TLS; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.
Needs work
DNS CAA Records
No CAA records found in the DNS tree for this domain. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorised CAs only, reducing the risk of misissued certificates.
No CAA records found in the DNS tree for this domain. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorised CAs only, reducing the risk of misissued certificates.
Needs work
DNS Configuration
Strengths: 4 nameservers configured (ns-2031.awsdns-61.co.uk, ns-205.awsdns-25.com, ns-949.awsdns-54.net, ns-1430.awsdns-50.org); NS records span 4 providers (co.uk, awsdns-25.com, awsdns-54.net, awsdns-50.org) — genuine redundancy; SOA record present and MNAME consistent with NS set; 2 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 2 A record(s). Issues: DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).
Strengths: 4 nameservers configured (ns-2031.awsdns-61.co.uk, ns-205.awsdns-25.com, ns-949.awsdns-54.net, ns-1430.awsdns-50.org); NS records span 4 providers (co.uk, awsdns-25.com, awsdns-54.net, awsdns-50.org) — genuine redundancy; SOA record present and MNAME consistent with NS set; 2 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 2 A record(s). Issues: DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).
Needs work
Security Headers
5/5 security headers present. Quality issues: CSP: 'unsafe-eval' allows eval() — weakens XSS protection.
5/5 security headers present. Quality issues: CSP: 'unsafe-eval' allows eval() — weakens XSS protection.
Needs work
Known Breaches
1 breach(es) found (1 verified). Total accounts affected: 3,883,455. Breaches: JobStreet (2012-03-07, 3,883,455 accounts).
1 breach(es) found (1 verified). Total accounts affected: 3,883,455. Breaches: JobStreet (2012-03-07, 3,883,455 accounts).
Needs work
security.txt (RFC 9116)
No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.
No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.
Needs work
MX Records & Mail Provider
Strengths: Mail handled by Proofpoint; 2 MX record(s) configured; Multiple MX records provide redundancy; Equal-priority MX records (10) — standard round-robin load balancing for Proofpoint.
Strengths: Mail handled by Proofpoint; 2 MX record(s) configured; Multiple MX records provide redundancy; Equal-priority MX records (10) — standard round-robin load balancing for Proofpoint.
Passed
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Passed
TLS Protocol Support
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
Passed
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 1/10 (within limit); DKIM configured (selectors: default, selector2, s1, s2, pp1).
Strengths: DMARC policy set to reject (strongest); DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 1/10 (within limit); DKIM configured (selectors: default, selector2, s1, s2, pp1).
Passed
HSTS Header
HSTS enabled: max-age=157680000s (1825 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
HSTS enabled: max-age=157680000s (1825 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
Passed
Cookie Security
Strengths: 1 cookie(s) analyzed; All cookies have Secure flag; All cookies have HttpOnly flag; All cookies have SameSite attribute.
Strengths: 1 cookie(s) analyzed; All cookies have Secure flag; All cookies have HttpOnly flag; All cookies have SameSite attribute.
Passed
CVE Exposure
Detected technologies: cloudflare. (cloudflare detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Detected technologies: cloudflare. (cloudflare detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Passed
Certificate Hygiene
Strengths: Certificate valid, 71 days remaining; Issued by Google Trust Services. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
Strengths: Certificate valid, 71 days remaining; Issued by Google Trust Services. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
Passed
Recommended actions 1+ items

Steps to improve jobstreet.com's security grade, ranked by impact.

1
Enable DNSSEC on your domain
DNS Configuration
1–3 days (depends on registrar) High

Without DNSSEC, DNS responses for jobstreet.com can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.

NIST 800-53SC-20
Secure name/address resolution service
How to fix this
1 Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2 Enable DNSSEC signing in your DNS provider dashboard
3 Add the DS record to your registrar for .com TLD
4 Verify: dig +dnssec jobstreet.com
AI Summary
What this means

jobstreet.com scored 85/100, demonstrating a strong security posture. Minor improvements are noted below.

Positive signals: MX Records & Mail Provider, TLS Configuration, TLS Protocol Support all passed.

3 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.

How jobstreet.com compares

Grade distribution across 2685 companies we've scanned. jobstreet.com scores better than 78% of them.

78th percentile
0 Percentile rank 100
88
A+
28
A
196
A-
202
B+
76
B
376
B-
138
C+
117
C
347
C-
123
D+
96
D
266
D-
632
F
jobstreet.com — Grade B (85/100) 2685 companies scanned
At a glance

Key data points from the scan.

TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest); DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 1/10 (within limit); DKIM configured (selectors: default, selector2, s1, s2, pp1).
SPF Record
Present
v=spf1 include:corp.spf.seek.com.au -all
Security Headers
5/5 present
All headers configured.
HSTS
Enabled
HSTS enabled: max-age=157680000s (1825 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 71 days remaining; Issued by Google Trust Services. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-2031.awsdns-61.co.uk, ns-205.awsdns-25.com, ns-949.awsdns-54.net, ns-1430.awsdns-50.org); NS records span 4 providers (co.uk, awsdns-25.com, awsdns-54.net, awsdns-50.org) — genuine redundancy; SOA record present and MNAME consistent with NS set; 2 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 2 A record(s). Issues: DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).