puppet.com

Checked 22 October 2026, 10:22 UTC · via 8.8.8.8
✗Problems found
27 passed 3 warnings 1 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf.protection.outlook.com include:mail.zendesk.com include:_spf.google.com include:_spfblock.salesforce.com ip4:194.46.129.148 ip4:213.120.212.50 ip4:192.28.148.112 ip4:208.86.168.7 ip4:135.84.68.123 ip4:206.152.14.54 -all
DNS lookups
5 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 5 of 10 DNS lookups #2
    SPF record needs 5 DNS lookups (limit is 10).
  • ✓ Ends with -all #3
    SPF record properly uses -all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

pass

p=reject (_dmarc.puppet.com)

Found

Record
v=DMARC1; p=reject; pct=100; rua=mailto:ymkfzyr1@ag.dmarcian.com; ruf=mailto:ymkfzyr1@fr.dmarcian.com; fo=1; adkim=s; aspf=s; rf=afrf; ri=86400
Found at
_dmarc.puppet.com
External report address
mailto:ymkfzyr1@ag.dmarcian.com (authorized)
External report address
mailto:ymkfzyr1@fr.dmarcian.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
pct100Percentage of mail the policy applies to
ruamailto:ymkfzyr1@ag.dmarcian.comAggregate report addresses
rufmailto:ymkfzyr1@fr.dmarcian.comFailure report addresses
adkimsDKIM alignment (r = relaxed, s = strict)
aspfsSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options
rfafrfFailure report format
ri86400Report interval (seconds)

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ 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:ymkfzyr1@ag.dmarcian.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: selector1, google, s1, s2

Found

Selectors
selector1, google, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits
googleRSA 2048 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: selector1, google, s1, s2 #7
    DKIM keys found for this domain with selectors: selector1, google, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: s2 (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

1 mail server

Found

PriorityHostRecordsReverse DNS
0puppet-com.mail.protection.outlook.comA 52.101.60.71 A 52.101.50.1 A 52.101.202.156 A 52.101.41.24 AAAA 2a01:111:f403:f807:: AAAA 2a01:111:f403:c902::3 AAAA 2a01:111:f403:c922::2 AAAA 2a01:111:f403:c927::7mail-bn0pr02cu00307.inbound.protection.outlook.com ✓ mail-co1pr05cu00401.inbound.protection.outlook.com ✓ mail-ph8pr21cu00204.inbound.protection.outlook.com ✓ mail-sj0pr03cu01600.inbound.protection.outlook.com ✓ mail-co1pr02cu00200.inbound.protection.outlook.com ✓ mail-sj0pr03cu01703.inbound.protection.outlook.com ✓ mail-bl0pr02cu00702.inbound.protection.outlook.com ✓ mail-bn0pr04cu00907.inbound.protection.outlook.com ✓

Checks

  • ✓ 1 MX record #9
    Found 1 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.
  • !
    Single MX host, no backup
    Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • ✓ At most 5 MX records #13
    Found 1 MX records, which is within the recommended range (1-5).
  • ✓ 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 8 MX addresss have a PTR record that resolves back to them.

TLS

fail

MTA-STS record without policy · TLS-RPT · DANE on 0 of 1 MX hosts

Found

MTA-STS record
v=STSv1; id=20231128151144
Policy URL
https://mta-sts.puppet.com/.well-known/mta-sts.txt
Policy error
Get "https://mta-sts.puppet.com/.well-known/mta-sts.txt": http: server gave HTTP response to HTTPS client
TLS-RPT record
v=TLSRPTv1; rua=mailto:ymkfzyr1@tls.us.dmarcian.com

DANE (TLSA records)

MX hostTLSADNSSEC
puppet-com.mail.protection.outlook.comnone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20231128151144.
  • ✗
    Policy not reachable
    The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: Get "https://mta-sts.puppet.com/.well-known/mta-sts.txt": http: server gave HTTP response to HTTPS client.
    #33
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:ymkfzyr1@tls.us.dmarcian.com
  • 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