SurfaceMap › j › jobvite.com

jobvite.com

Checked 2026-10-22 09:24 UTC · first added 2026-10-21
✗Problems found Score 63 of 100

Domain & DNS

warn

26 passed 3 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers !SOA !DNSSEC !Records

Problems

  • !
    Unusual SOA timers
    SOA · expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 2h, retry 15m, expire 1d, negative TTL 5m.
    #23
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: MX (30s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 5m; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for jobvite.com ›

Mail

fail

22 passed 6 warn 1 failed

Areas

✓SPF !DMARC ✗DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • ✗
    Weak DKIM key
    DKIM · RSA keys shorter than 1024 bits can be cracked and are ignored by receivers (RFC 8301): default (768 bits). Rotate to a 2048-bit key.
    #23
  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: jobvite-com.p10.spamhero.com, jobvite-com.p20.spamhero.net, jobvite-com.p30.spamhero.net, jobvite-com.p40.spamhero.net
    #11
  • !
    Applies to 0% of mail
    DMARC · DMARC policy only applies to 0% of failing mail (pct=0). Raise pct to 100 once you are confident in your setup.
    #18
  • !
    Key in test mode
    DKIM · These keys have t=y, so receivers treat DKIM failures as a test: default. Remove t=y once DKIM works.
    #24
  • !
    Not configured
    TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32

Recent checks

✗

Full report

Mail report for jobvite.com ›