salesforce-dns.comDNS health report
Testing every nameserver. This takes a few seconds.
Testing every nameserver. This takes a few seconds.
Failures and warnings, most serious first, each with what to do.
The domain has no DMARC record. Receivers decide on their own what to do with mail that fails SPF and DKIM, and you get no reports about who sends in your name. Large mail providers require DMARC from bulk senders.
How to fix: Add a TXT record at _dmarc.salesforce-dns.com. Start by only collecting reports: v=DMARC1; p=none; rua=mailto:you@salesforce-dns.com
Nameservers have different SOA serials. Some have not received the latest zone yet.
How to fix: Wait for the zone transfer, or check NOTIFY and transfer settings between primary and secondaries.
www.salesforce-dns.com does not resolve to any address. Visitors who type the www form will get an error.
How to fix: Add an A/AAAA record or a CNAME for www.
The .com zone lists 10 nameservers for salesforce-dns.com.
10 nameservers are listed. At least two are required.
Every nameserver that needs a glue record has one.
All 20 nameserver addresses answered over UDP.
All reachable nameservers answered over TCP.
Every reachable nameserver answers authoritatively for the zone.
The NS records at the parent and in the zone match.
No nameserver offers recursion to the public.
Nameservers have different SOA serials. Some have not received the latest zone yet.
How to fix: Wait for the zone transfer, or check NOTIFY and transfer settings between primary and secondaries.
The zone's SOA record.
The domain has no MX records, so it does not receive e-mail (or mail falls back to the A record).
How to fix: If the domain should receive e-mail, add MX records. If not, publish a null MX record (0 .).
The domain has no DMARC record. Receivers decide on their own what to do with mail that fails SPF and DKIM, and you get no reports about who sends in your name. Large mail providers require DMARC from bulk senders.
How to fix: Add a TXT record at _dmarc.salesforce-dns.com. Start by only collecting reports: v=DMARC1; p=none; rua=mailto:you@salesforce-dns.com
The domain has one SPF record.
Checking this record takes 0 of the 10 DNS lookups a receiver allows, includes within includes counted.
Mail from servers the record does not list fails SPF (-all).
www.salesforce-dns.com does not resolve to any address. Visitors who type the www form will get an error.
How to fix: Add an A/AAAA record or a CNAME for www.
salesforce-dns.com itself has no A or AAAA record. Visitors who type the domain without www will get an error.
How to fix: Add an A/AAAA record for the bare domain, or an ALIAS/ANAME record if your DNS host offers one.
Report generated in 295 ms.
Every nameserver name resolves to an address.
Every nameserver has an IPv6 address.
No DS record at the parent zone. The domain is not signed with DNSSEC.
No nameserver reveals its software version.
Nameservers are spread over 8 IPv4 networks.
The primary nameserver dns01.salesforce.com is one of the listed nameservers.
Refresh is 1800 s (30 minutes), within the usual range.
Retry is 900 s (15 minutes), within the usual range.
Expire is 2592000 s (30 days), outside the usual range of 2 to 4 weeks. This matters only if your secondary nameservers copy the zone with zone transfers.
Minimum (negative cache TTL) is 1800 s (30 minutes), within the usual range.
No DKIM key was found under 38 common selectors. That does not prove there is none: DNS cannot list the selectors of a domain.
How to fix: Find the selector in the DKIM-Signature header of a message you sent (the s= value) and check it on the DKIM page of this domain.