SurfaceMap › s › sysaid.com

sysaid.com

Checked 2026-10-22 10:53 UTC · first added 2026-10-21
✗Problems found Score 62 of 100

Domain & DNS

warn

27 passed 1 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    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

Recent checks

!

Full report

Domain & DNS report for sysaid.com ›

Mail

fail

22 passed 5 warn 2 failed

Areas

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

Problems

  • ✗
    21 DNS lookups, over the limit of 10
    SPF · SPF record needs 21 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • ✗
    No 'all' mechanism
    SPF · SPF record doesn't have an 'all' mechanism. Add -all or ~all at the end of your SPF record.
    #3
  • !
    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
  • !
    Subdomains unprotected (sp=none)
    DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: google (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 sysaid.com ›