vonage.com

Checked 22 October 2026, 11:23 UTC · via 8.8.8.8
!Passed with warnings
25 passed 4 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf.sendinblue.com include:_spf.google.com include:et._spf.pardot.com ip4:69.59.224.0/19 ip4:216.115.22.0/24 ip4:216.115.25.0/24 ip4:216.27.209.51/32 ip4:69.176.76.197/32 include:spf1.vonage.com ip4:52.1.235.217/32 ip4:52.1.252.231/32 ip4:69.176.73.75/32 ip4:72.9.193.74/32 ip4:64.106.227.0/24 ip4:67.216.78.0/24 ip4:99.80.30.16/32 ip4:166.78.227.202/32 ip4:166.78.227.203/32 include:mktomail.com include:amazonses.com ip4:163.47.182.0/24 ip4:132.226.58.160/32 ip4:129.80.56.29/32 ip4:141.148.64.92/32 include:spf.protection.outlook.com include:_spf.createsend.com ~all
DNS lookups
8 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 8 of 10 DNS lookups #2
    SPF record needs 8 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.vonage.com)

Found

Record
v=DMARC1; p=reject; rua=mailto:dmarc_rua@vonage.com; ruf=mailto:dmarc_rua@vonage.com,mailto:dmarc_ruf@vonage.com
Found at
_dmarc.vonage.com
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:dmarc_rua@vonage.comAggregate report addresses
rufmailto:dmarc_rua@vonage.com,mailto:dmarc_ruf@vonage.comFailure report addresses

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_rua@vonage.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: mail, selector1, s1, s2

Found

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

Checks

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

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
10vonage-com.mail.protection.outlook.comA 52.101.50.10 A 52.101.60.68 A 52.101.40.56 A 52.101.11.17 AAAA 2a01:111:f403:f90a::8 AAAA 2a01:111:f403:c91d::b AAAA 2a01:111:f403:f804::7 AAAA 2a01:111:f403:c95d::4mail-mw2pr02cu00502.inbound.protection.outlook.com ✓ mail-bnypr02cu00104.inbound.protection.outlook.com ✓ mail-cy7pr05cu00100.inbound.protection.outlook.com ✓ mail-sn1pr0501cu00301.inbound.protection.outlook.com ✓ mail-bn0pr05cu00100.inbound.protection.outlook.com ✓ mail-mw2pr02cu00603.inbound.protection.outlook.com ✓ mail-co2pr03cu00307.inbound.protection.outlook.com ✓ mail-ph6pr04cu00104.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

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
vonage-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

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