SurfaceMap › y › yardbarker.com

yardbarker.com

Checked 2026-10-22 11:37 UTC · first added 2026-10-21
!Passed with warnings Score 70 of 100

Domain & DNS

warn

22 passed 3 warn 0 failed

Areas

iRegistration !Delegation iNameservers !SOA !DNSSEC iRecords

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: ns3.dnsmadeeasy.com, ns4.dnsmadeeasy.com. ns0.dnsmadeeasy.com, ns1.dnsmadeeasy.com, ns2.dnsmadeeasy.com, ns3.dnsmadeeasy.com, ns4.dnsmadeeasy.com report NS ns0.dnsmadeeasy.com ns1.dnsmadeeasy.com ns2.dnsmadeeasy.com ns3.dnsmadeeasy.com ns4.dnsmadeeasy.com.
    #7
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 12h, retry 1h, expire 14d, negative TTL 3m.
    #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

Recent checks

!

Full report

Domain & DNS report for yardbarker.com ›

Mail

warn

24 passed 7 warn 0 failed

Areas

✓SPF !DMARC !DKIM !DNSSEC !MX !TLS ✓BIMI

Problems

  • !
    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
  • !
    More than 5 MX records
    MX · Found 7 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Key in test mode
    DKIM · These keys have t=y, so receivers treat DKIM failures as a test: mail. Remove t=y once DKIM works.
    #24
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc-reports@bettercollective.com (needs yardbarker.com._report._dmarc.bettercollective.com). Ask the report provider to publish the record, or check the address.
    #29
  • !
    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 yardbarker.com ›