reedsy.com

Checked 22 October 2026, 10:30 UTC · via 8.8.8.8
!Passed with warnings
16 passed 5 warnings 0 failed 4 info

SPF

info

DNS query for reedsy.com failed: read udp 46.225.38.91:46512->8.8.8.8:53: i/o timeout

Checks

  • i
    Could not be checked
    The SPF lookup failed, so this could not be checked: DNS query for reedsy.com failed: read udp 46.225.38.91:46512->8.8.8.8:53: i/o timeout
    #6

DMARC

warn

p=quarantine (_dmarc.reedsy.com)

Found

Record
v=DMARC1; p=quarantine; pct=100; fo=1; adkim=r; aspf=r; ri=3600; rua=mailto:dmarc@reedsy.com,mailto:re+145651b2e960@inbound.dmarcdigests.com
Found at
_dmarc.reedsy.com
External report address
mailto:re+145651b2e960@inbound.dmarcdigests.com (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
pct100Percentage of mail the policy applies to
ruamailto:dmarc@reedsy.com,mailto:re+145651b2e960@inbound.dmarcdigests.comAggregate report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options
ri3600Report interval (seconds)

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc@reedsy.com, mailto:re+145651b2e960@inbound.dmarcdigests.com
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: google

Found

Selectors
google
_domainkey
NOERROR
SelectorKeyFlags
googleRSA 1024 bits

Checks

  • ✓ Keys found: google #7
    DKIM keys found for this domain with selectors: google
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: google (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

7 mail servers

Found

PriorityHostRecordsReverse DNS
1ASPMX.L.GOOGLE.comA 142.251.127.27 AAAA 2a00:1450:4001:c21::1alcfrai-in-f27.1e100.net ✓ lcfrai-in-f26.1e100.net ✓
3ALT1.ASPMX.L.GOOGLE.comA 142.250.147.26 AAAA 2a00:1450:4025:c01::1brd-in-f26.1e100.net ✓ rd-in-f27.1e100.net ✓
3ALT2.ASPMX.L.GOOGLE.comA 172.253.152.26 AAAA 2a00:1450:4010:c22::1ayulpptr-in-f26.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
5ASPMX2.GOOGLEMAIL.comA 142.250.147.27 AAAA 2a00:1450:4025:c01::1ard-in-f27.1e100.net ✓ rd-in-f26.1e100.net ✓
5ASPMX3.GOOGLEMAIL.comA 172.253.152.27 AAAA 2a00:1450:4010:c22::1ayulpptr-in-f27.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
5ASPMX4.GOOGLEMAIL.comA 192.179.20.27 AAAA 2404:6800:4000:1027::1ancboms-in-f27.1e100.net ✓ ncboms-in-f26.1e100.net ✓
5ASPMX5.GOOGLEMAIL.comA 192.178.158.26 AAAA 2404:6800:4013:813::1blcdels-in-f26.1e100.net ✓ lcdels-in-f27.1e100.net ✓

Checks

  • ✓ 7 MX records #9
    Found 7 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • ✓ Redundant MX hosts #12
    Found 7 MX records, which provides redundancy for email delivery.
  • !
    More than 5 MX records
    Found 7 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 14 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 7 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
ASPMX.L.GOOGLE.comnone-
ALT1.ASPMX.L.GOOGLE.comnone-
ALT2.ASPMX.L.GOOGLE.comnone-
ASPMX2.GOOGLEMAIL.comnone-
ASPMX3.GOOGLEMAIL.comnone-
ASPMX4.GOOGLEMAIL.comnone-
ASPMX5.GOOGLEMAIL.comnone-

Checks

  • !
    Not configured
    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
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38