hubstaff.com

Checked 22 October 2026, 09:13 UTC · via 8.8.8.8
!Passed with warnings
23 passed 5 warnings 0 failed 4 info

SPF

warn

SPF record published

Found

Record
v=spf1 a include:_spf.google.com include:spf.mandrillapp.com include:sendgrid.net include:emsd1.com include:8683234.spf03.hubspotemail.net -all
DNS lookups
7 of 10
Void lookups
0 of 2
Problem
include:8683234.spf03.hubspotemail.net could not be resolved: DNS query for 8683234.spf03.hubspotemail.net failed: read udp 46.225.38.91:44336->8.8.8.8:53: i/o timeout

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • !
    7 of 10 DNS lookups, with problems
    SPF record needs 7 DNS lookups (limit is 10). Problems found: include:8683234.spf03.hubspotemail.net could not be resolved: DNS query for 8683234.spf03.hubspotemail.net failed: read udp 46.225.38.91:44336->8.8.8.8:53: i/o timeout.
    #2
  • ✓ 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

warn

p=reject (_dmarc.hubstaff.com)

Found

Record
v=DMARC1; p=reject; sp=none; rua=mailto:dmarc_aggregate_analyser+f974a42707ab390aa2fe778a115d7772@zerobounce.net,mailto:re+0b7e4f254716@inbound.dmarcdigests.com; ruf=mailto:dmarc_forensics_analyser+f974a42707ab390aa2fe778a115d7772@zerobounce.net; rf=afrf; pct=100; ri=86400; fo=1;
Found at
_dmarc.hubstaff.com
External report address
mailto:dmarc_aggregate_analyser+f974a42707ab390aa2fe778a115d7772@zerobounce.net (authorized)
External report address
mailto:re+0b7e4f254716@inbound.dmarcdigests.com (authorized)
External report address
mailto:dmarc_forensics_analyser+f974a42707ab390aa2fe778a115d7772@zerobounce.net (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:dmarc_aggregate_analyser+f974a42707ab390aa2fe778a115d7772@zerobounce.net,mailto:re+0b7e4f254716@inbound.dmarcdigests.comAggregate report addresses
rufmailto:dmarc_forensics_analyser+f974a42707ab390aa2fe778a115d7772@zerobounce.netFailure report addresses
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:dmarc_aggregate_analyser+f974a42707ab390aa2fe778a115d7772@zerobounce.net, mailto:re+0b7e4f254716@inbound.dmarcdigests.com
  • !
    Subdomains unprotected (sp=none)
    DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: google, s1, s2

Found

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

Checks

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

info

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

Checks

  • i
    Could not be checked
    The DNSSEC lookup failed, so this could not be checked: DNS query for hubstaff.com failed: read udp 46.225.38.91:54897->8.8.8.8:53: i/o timeout
    #8

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
1smtp.google.comA 142.251.127.27 A 142.251.127.26lcfrai-in-f27.1e100.net ✓ lcfrai-in-f26.1e100.net ✓

Checks

  • ✓ 1 MX record #9
    Found 1 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: smtp.google.com
    #11
  • !
    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 2 MX addresss have a PTR record that resolves back to them.

TLS

info

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

Found

TLS-RPT record
v=TLSRPTv1; rua=mailto:dev-sec-ops@hubstaff.com

DANE (TLSA records)

MX hostTLSADNSSEC
smtp.google.comnone-
Lookup error: DNS query for _mta-sts.hubstaff.com failed: read udp 46.225.38.91:38854->8.8.8.8:53: i/o timeout

Checks

  • i
    Could not be checked
    The MTA-STS lookup failed, so this could not be checked: DNS query for _mta-sts.hubstaff.com failed: read udp 46.225.38.91:38854->8.8.8.8:53: i/o timeout
    #32
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:dev-sec-ops@hubstaff.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