orkin.com

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

SPF

warn

SPF record published

Found

Record
v=spf1 ip4:146.88.149.0/24 ip4:3.93.157.0/24 ip4:18.208.124.128/25 ip4:23.23.237.213 ip4:23.253.182.0/23 ip4:35.190.247.0/24 ip4:35.191.0.0/16 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:50.23.218.192/27 ip4:50.31.36.197 ip4:50.31.36.199 ip4:50.31.36.205 ip4:50.31.36.208 ip4:50.31.36.213 ip4:50.31.44.111 ip4:50.31.57.60 ip4:50.31.60.1 ip4:50.207.4.0/24 ip4:50.232.105.0/24 ip4:52.0.20.102 ip4:52.100.0.0/14 ip4:54.88.201.24 ip4:54.173.229.38 ip4:54.174.52.0/24 ip4:54.174.53.128/30 include:spf1.orkin.com -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.
  • !
    Broad IP ranges
    These ranges authorize tens of thousands of addresses or more: ip4:40.92.0.0/15, ip4:52.100.0.0/14. Check that you really own and send from all of them.
    #27

DMARC

warn

p=quarantine (_dmarc.orkin.com)

Found

Record
v=DMARC1; p=quarantine; pct=100; sp=quarantine; rua=mailto:pj5zl-9388@rua.dmarc.emailanalyst.com; ruf=mailto:pj5zl-9388@ruf.dmarc.emailanalyst.com; adkim=r; aspf=r; ri=43200
Found at
_dmarc.orkin.com
External report address
mailto:pj5zl-9388@rua.dmarc.emailanalyst.com (authorized)
External report address
mailto:pj5zl-9388@ruf.dmarc.emailanalyst.com (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spquarantineSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:pj5zl-9388@rua.dmarc.emailanalyst.comAggregate report addresses
rufmailto:pj5zl-9388@ruf.dmarc.emailanalyst.comFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
ri43200Report 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:pj5zl-9388@rua.dmarc.emailanalyst.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

pass

Selectors: selector1, s1, s2

Found

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

Checks

  • ✓ Keys found: selector1, s1, s2 #7
    DKIM keys found for this domain with selectors: selector1, s1, s2
  • ✓ Strong keys #23
    DKIM keys are strong enough: selector1: RSA 2048 bits; s1: RSA 2048 bits; s2: RSA 2048 bits.
  • ✓ 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

pass

2 mail servers

Found

PriorityHostRecordsReverse DNS
10orkin-com.mail.protection.outlook.comA 52.101.41.54 A 52.101.60.185 A 52.101.9.84 A 52.101.42.14 AAAA 2a01:111:f403:c902::3 AAAA 2a01:111:f403:f804::7 AAAA 2a01:111:f403:c946::12 AAAA 2a01:111:f403:c902::5mail-sj2pr05cu00506.inbound.protection.outlook.com ✓ mail-bnypr03cu00201.inbound.protection.outlook.com ✓ mail-mn0pr04cu00204.inbound.protection.outlook.com ✓ mail-mw2pr04cu00106.inbound.protection.outlook.com ✓ mail-sj0pr03cu01703.inbound.protection.outlook.com ✓ mail-co2pr03cu00307.inbound.protection.outlook.com ✓ mail-chtpr21cu00102.inbound.protection.outlook.com ✓ mail-sj2pr05cu00505.inbound.protection.outlook.com ✓
20orkin-com.mail.protection.outlook.comA 52.101.9.84 A 52.101.60.185 A 52.101.42.14 A 52.101.41.54 AAAA 2a01:111:f403:f909::1 AAAA 2a01:111:f403:f90d::1 AAAA 2a01:111:f403:f907:: AAAA 2a01:111:f403:f803::1mail-mn0pr04cu00204.inbound.protection.outlook.com ✓ mail-bnypr03cu00201.inbound.protection.outlook.com ✓ mail-mw2pr04cu00106.inbound.protection.outlook.com ✓ mail-sj2pr05cu00506.inbound.protection.outlook.com ✓ mail-bn0pr02cu00301.inbound.protection.outlook.com ✓ mail-sn1pr0501cu00301.inbound.protection.outlook.com ✓ mail-dm2pr02cu00100.inbound.protection.outlook.com ✓ mail-byapr05cu00601.inbound.protection.outlook.com ✓

Checks

  • ✓ 2 MX records #9
    Found 2 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 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 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 16 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
orkin-com.mail.protection.outlook.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

pass

https://media.orkin.com/logos/orkin-logo-xs.svg

Found

Record
v=BIMI1; a=https://media.orkin.com/support/orkin-email.pem; l=https://media.orkin.com/logos/orkin-logo-xs.svg; avp=brand
Found at
default._bimi.orkin.com
Logo
https://media.orkin.com/logos/orkin-logo-xs.svg
Certificate
https://media.orkin.com/support/orkin-email.pem

Checks

  • ✓ Logo and certificate published #38
    BIMI logo: https://media.orkin.com/logos/orkin-logo-xs.svg; certificate: https://media.orkin.com/support/orkin-email.pem
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.