sendgrid.com

Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns11.dnsmadeeasy.com, ns12.dnsmadeeasy.com, ns13.dnsmadeeasy.com, ns14.dnsmadeeasy.com, ns15.dnsmadeeasy.com; only in the zone: ns-2039.awsdns-62.co.uk, ns-506.awsdns-63.com, ns-697.awsdns-23.net. ns-1389.awsdns-45.org, ns-2039.awsdns-62.co.uk, ns-506.awsdns-63.com, ns-697.awsdns-23.net report NS ns-1389.awsdns-45.org ns-2039.awsdns-62.co.uk ns-506.awsdns-63.com ns-697.awsdns-23.net. ns11.dnsmadeeasy.com, ns12.dnsmadeeasy.com, ns13.dnsmadeeasy.com, ns14.dnsmadeeasy.com, ns15.dnsmadeeasy.com report NS ns10.dnsmadeeasy.com ns11.dnsmadeeasy.com ns12.dnsmadeeasy.com ns13.dnsmadeeasy.com ns14.dnsmadeeasy.com ns15.dnsmadeeasy.com.

SOA · The nameservers serve different versions of the zone: 1 on ns-1389.awsdns-45.org (205.251.197.109), ns-1389.awsdns-45.org (2600:9000:5305:6d00::1), ns-2039.awsdns-62.co.uk (205.251.199.247), ns-2039.awsdns-62.co.uk (2600:9000:5307:f700::1), ns-506.awsdns-63.com (205.251.193.250), ns-506.awsdns-63.com (2600:9000:5301:fa00::1), ns-697.awsdns-23.net (205.251.194.185), ns-697.awsdns-23.net (2600:9000:5302:b900::1); 2011112307 on ns11.dnsmadeeasy.com (208.80.124.4), ns11.dnsmadeeasy.com (2600:1801:11::1), ns12.dnsmadeeasy.com (208.80.126.4), ns12.dnsmadeeasy.com (2600:1802:12::1), ns13.dnsmadeeasy.com (208.80.125.4), ns13.dnsmadeeasy.com (2600:1801:13::1), ns14.dnsmadeeasy.com (208.80.127.4), ns14.dnsmadeeasy.com (2600:1802:14::1), ns15.dnsmadeeasy.com (208.94.149.4), ns15.dnsmadeeasy.com (2600:1800:15::1). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.

DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.

Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m30s). Low TTLs are useful just before a planned change.

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.

TLS · 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.