hubspot.com
Receivers are told to reject mail that fails authentication for this domain.
Receivers are told to reject mail that fails authentication for this domain. Keep watching aggregate reports so a new sending service does not silently start failing.
Score held up: DMARC is enforcing at p=reject, so nobody else can send as this domain. That is the hard part, and it is done. What is left below is about your own mail arriving, not about anyone spoofing you.
133 DNS queries · 506 ms
- 1Selector 'google' uses a 1024-bit RSA keyRotate to 2048-bit at your next key rotation.
- 2Selector 'mandrill' uses a 1024-bit RSA keyRotate to 2048-bit at your next key rotation.
- 3Selector 's2' uses a 1024-bit RSA keyRotate to 2048-bit at your next key rotation.
- 4Selector 'qualtrics' uses a 1024-bit RSA keyRotate to 2048-bit at your next key rotation.
Identity ·Sending services detected
Read from your SPF includes and MX hosts, then checked for a published DKIM key.
Identity ·DMARC
- Policy
- reject
- Coverage
- 100%
- Alignment
- dkim=r spf=r
Identity ·DKIM
111 selectors probed
googleGoogle WorkspaceRSA 1024mandrillMailchimp TransactionalRSA 1024s1SendGridRSA 2048s2SendGridRSA 1024qualtricsQualtricsRSA 1024m1MarketoRSA 1024Identity ·SPF
Worst-case evaluation across every include.
- include:_hspf.hubspot.com
- include:_hspf1.hubspot.com
- include:_hspf2.hubspot.com
- include:_hspf3.hubspot.com
Findings (10)
MediumSelector 'google' uses a 1024-bit RSA key›
1024-bit is the RFC 8301 floor, not a good target. 2048-bit is the current recommendation and is universally supported.
Rotate to 2048-bit at your next key rotation.
RFC 8301
MediumSelector 'mandrill' uses a 1024-bit RSA key›
1024-bit is the RFC 8301 floor, not a good target. 2048-bit is the current recommendation and is universally supported.
Rotate to 2048-bit at your next key rotation.
RFC 8301
MediumSelector 's2' uses a 1024-bit RSA key›
1024-bit is the RFC 8301 floor, not a good target. 2048-bit is the current recommendation and is universally supported.
Rotate to 2048-bit at your next key rotation.
RFC 8301
MediumSelector 'qualtrics' uses a 1024-bit RSA key›
1024-bit is the RFC 8301 floor, not a good target. 2048-bit is the current recommendation and is universally supported.
Rotate to 2048-bit at your next key rotation.
RFC 8301
MediumSelector 'm1' uses a 1024-bit RSA key›
1024-bit is the RFC 8301 floor, not a good target. 2048-bit is the current recommendation and is universally supported.
Rotate to 2048-bit at your next key rotation.
RFC 8301
LowNo explicit subdomain policy (sp=)›
Subdomains inherit p=, which is usually what you want. Setting 'sp=reject' explicitly protects unused subdomains even while the parent is still at p=none.
Consider adding 'sp=reject' if no subdomain sends mail.
LowNo MTA-STS policy›
Without MTA-STS, mail to your domain can be downgraded to plaintext by an active network attacker, because SMTP's STARTTLS is opportunistic by default.
Publish a TXT record at _mta-sts.hubspot.com and a policy file at https://mta-sts.hubspot.com/.well-known/mta-sts.txt.
RFC 8461
LowNo TLS-RPT record›
Sending servers have no address to report TLS failures on mail to your domain, so transport problems stay invisible to you until someone complains.
Publish 'v=TLSRPTv1; rua=mailto:<address>' at _smtp._tls.hubspot.com.
RFC 8460
LowNo CAA record›
Any certificate authority in the world may issue a certificate for this domain. A mis-issued certificate can be used to intercept mail on the wire and to impersonate your domain over HTTPS.
Publish a CAA record naming your certificate authority, for example: 0 issue "letsencrypt.org"
RFC 8659
InfoEligible for DANE›
Your zone is signed, which is the hard prerequisite for DANE. Publishing TLSA records for your MX hosts would let sending servers pin your certificates without relying on the public CA system.
Publish a TLSA record at _25._tcp.<each MX host> matching your MX certificate.
RFC 7672
Show 10 passing checks
PassAggregate reporting is configured›
Aggregate reports are requested at: [email protected].
PassExternal report destination ag.dmarcian.com is correctly authorised›
Authorised by hubspot.com._report._dmarc.ag.dmarcian.com
PassExternal report destination fr.dmarcian.com is correctly authorised›
Authorised by hubspot.com._report._dmarc.fr.dmarcian.com
PassDMARC policy is p=reject›
Mail failing authentication is rejected outright. This is the correct end state.
PassSPF lookup count is healthy (4/10)›
Worst-case evaluation stays within the limit with headroom to spare.
PassGoogle Workspace's DKIM key is published at google._domainkey›
Detected via MX smtp.google.com. A valid public key for this service is published at google._domainkey.hubspot.com.
Pass6 DKIM key(s) published›
Found at: google, m1, mandrill, qualtrics, s1, s2.
PassSelector 's1' uses a 2048-bit RSA key›
Key length meets current guidance.
PassBIMI is published with a certificate reference›
The record at default._bimi.hubspot.com names a logo and a Verified Mark Certificate (a=), and DMARC is enforcing, which BIMI requires. We read the record only; the logo and certificate themselves were not fetched or checked.
PassZone is signed and validates›
A validating resolver reported this zone's answers as authenticated. Resolvers that validate DNSSEC reject a tampered answer for your SPF, DKIM and DMARC records rather than pass it on. This also makes DANE available to you.
Transport and zone
Where your mail lands, and whether the DNS carrying your records can be trusted.
This is the configuration. It is not the whole picture.
A DNS scan cannot tell you whether hubspot.com’s mail actually aligns, because alignment is decided per message at the receiver. Collect DMARC aggregate reports to see every source sending as this domain.