warning johndball.com
There were some non-critical problems detected with
the configuration of this domain.
Depending on how you configured your mail-flow, this could be
a source of mail delivery issues.
Overly large TXT response can cause problems for many senders. To avoid this, either decrease the number of TXT records or reduce their content.
info_outline
The following IP addresses are taken from the includes and IP4/IP6 directives within this domains SPF record.johndball.com. 50.211.39.27 _spf.google.com _netblocks.google.com 35.190.247.0/24 64.233.160.0/19 66.102.0.0/20 66.249.80.0/20 72.14.192.0/18 74.125.0.0/16 108.177.8.0/21 173.194.0.0/16 209.85.128.0/17 216.58.192.0/19 216.239.32.0/19 _netblocks2.google.com 2001:4860:4000::/36 2404:6800:4000::/36 2607:f8b0:4000::/36 2800:3f0:4000::/36 2a00:1450:4000::/36 2c0f:fb50:4000::/36 _netblocks3.google.com 172.217.0.0/19 172.217.32.0/20 172.217.128.0/19 172.217.160.0/20 172.217.192.0/19 172.253.56.0/21 172.253.112.0/20 108.177.96.0/19 35.191.0.0/16 130.211.0.0/22
done
Domain should have at least 2 NS servers.
done
Naked domain must be an A record (not CNAME).
done
Every name server must reply with exactly the same TXT DKIM records.
done
Every name server must reply with exactly the same TXT DMARC records.
done
Every name server must reply with exactly the same CNAME records.
done
Every name server must reply with exactly the same NS records.
done
Every name server must reply with exactly the same MX records.
done
Every name server must reply with exactly the same TXT records.
done
DKIM authentication DNS setup.
done
Formatting of DMARC policies.
done
SPF must allow Google servers to send mail on behalf of your domain.
done
MX lookup must fit in one UDP response packet.
Did this tool solve your problem ? Submit feedback.