ipinfo.io

ipinfo.io · Last checked 2026-10-04 02:11 UTC

ipinfo.io

Good, with 2 things to fix

ipinfo.io scored 84/100 (grade B). The main issues are DKIM key shorter than 2048 bits and SPF is close to the 10-lookup limit. Detected senders: Google Workspace, HubSpot, Mailgun and Zendesk.

Checked 2026-10-04 02:11 UTC · fresh check

2 passed2 need attention0 failing4 for informationDetected senders: Google Workspace, HubSpot, Mailgun, Zendesk
Fix this firstThe change with the biggest effect

Reduce SPF DNS lookups

Evaluating SPF for ipinfo.io takes 8 DNS lookups including nested includes; receivers stop at 10 and fail SPF. Every include belongs to a detected provider; move some senders to a subdomain with its own SPF record. Changes: HubSpot has no SPF include to add; it authenticates through its own return-path domain or DKIM. Replaced ~all with -all so mail from servers not listed is rejected.

TypeTXT
Name / Host
ipinfo.io

Some DNS providers want “@” here instead of the full domain.

Value
v=spf1 include:_spf.google.com include:mailgun.org include:24091853.spf01.hubspotemail.net include:mail.zendesk.com -all
Replaces
v=spf1 include:_spf.google.com include:mailgun.org include:24091853.spf01.hubspotemail.net include:mail.zendesk.com ~all

How to apply it

  1. Sign in where your domain’s DNS is managed. This is often where you bought the domain, such as Cloudflare, GoDaddy or Namecheap.
  2. Find the existing TXT record with that name and replace its value.
  3. Save, then come back and re-check. DNS changes can take up to a few hours to show.

All checks

MXCan servers find your inbox?No issues foundPass

Nothing to report.

SPFWho may send as you?SPF is close to the 10-lookup limitNeeds attention
  • Warning: SPF is close to the 10-lookup limit

    Evaluating the SPF record for ipinfo.io needs 8 of the 10 allowed DNS lookups. Adding one more service, or a provider growing its own record, will break SPF.

    How to fix this
  • Info: SPF ends in softfail (~all)

    "~all" is common and works well with DMARC. "-all" is stricter; switch when you are sure every sender is listed.

DKIMAre your emails signed?DKIM key shorter than 2048 bitsNeeds attention
  • Warning: DKIM key shorter than 2048 bits

    google (1024-bit) uses an RSA key below 2048 bits. Short keys can be factored and some receivers treat them as weak. Rotate to a 2048-bit key at your sending provider.

  • Pass: DKIM key published

    ipinfo.io publishes a DKIM key under google.

DMARCWhat happens to fakes?DMARC policy is quarantine; consider rejectInfo
  • Info: DMARC policy is quarantine; consider reject

    Failing mail goes to spam rather than being refused. When reports show no legitimate failures, reject gives the strongest protection.

    How to fix this
AlignmentDoes it match your From?No issues foundPass

Nothing to report.

BIMICan inboxes show your logo?No BIMI recordInfo
  • Info: No BIMI record

    No BIMI record at default._bimi.ipinfo.io. BIMI is optional: it shows your logo next to your mail in supporting inboxes once DMARC is enforced.

    How to fix this
MTA-STSIs mail to you encrypted?No MTA-STS recordInfo
  • Info: No MTA-STS record

    No MTA-STS record at _mta-sts.ipinfo.io. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.

    How to fix this
TLS-RPTWill you hear about failures?No TLS-RPT recordInfo
  • Info: No TLS-RPT record

    No TLS reporting record at _smtp._tls.ipinfo.io. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.

    How to fix this

Other fixes

Strengthen the DMARC policyTXT

Rejects mail that fails DMARC, the strongest protection against spoofing.

TypeTXT
Name / Host
_dmarc.ipinfo.io

Some DNS providers want just “_dmarc” here.

Value
v=DMARC1; p=reject; rua=mailto:re+f8005e16b411@inbound.dmarcdigests.com; adkim=r; aspf=r
Replaces
v=DMARC1; p=quarantine; pct=100; rua=mailto:re+f8005e16b411@inbound.dmarcdigests.com; fo=1

Publish the MTA-STS recordTXT

Tells sending servers that ipinfo.io publishes an MTA-STS policy at https://mta-sts.ipinfo.io/.well-known/mta-sts.txt. Change the id whenever the policy file changes.

TypeTXT
Name / Host
_mta-sts.ipinfo.io

Some DNS providers want just “_mta-sts” here.

Value
v=STSv1; id=202610040211

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.ipinfo.io. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.

Location
https://mta-sts.ipinfo.io/.well-known/mta-sts.txt
Contents
version: STSv1
mode: testing
mx: aspmx.l.google.com
mx: alt1.aspmx.l.google.com
mx: alt2.aspmx.l.google.com
mx: alt3.aspmx.l.google.com
mx: alt4.aspmx.l.google.com
max_age: 604800

Set up a TLS report addressinstruction

Sending servers will report TLS failures when delivering to ipinfo.io, which you need before enforcing MTA-STS. The address must accept TLS reports; a DMARC report address does not necessarily do so.

Applies to: _smtp._tls.ipinfo.io

  1. Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@ipinfo.io, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.ipinfo.io with the value v=TLSRPTv1; rua=mailto:<that address>.

Prepare BIMIinstruction

BIMI shows your logo next to messages in supporting inboxes, but only for mail that passes DMARC under an enforced policy.

Applies to: default._bimi.ipinfo.io

  1. Enforce DMARC first: p=quarantine or p=reject at 100% (no pct below 100). 2. Convert your logo to an SVG Tiny PS file and host it over HTTPS, for example https://ipinfo.io/bimi/logo.svg. 3. For Gmail and Apple Mail, obtain a VMC or CMC certificate for the logo. 4. Publish a TXT record at default._bimi.ipinfo.io with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.