latam.com

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: bill.ns.cloudflare.com: "2026.10.2"; rachel.ns.cloudflare.com: "2026.10.2". Hide or replace the version string.

SOA · The nameservers serve different versions of the zone: 1 on ns-cloud-e1.googledomains.com (216.239.32.110), ns-cloud-e1.googledomains.com (2001:4860:4802:32::6e), ns-cloud-e2.googledomains.com (216.239.34.110), ns-cloud-e2.googledomains.com (2001:4860:4802:34::6e), ns-cloud-e3.googledomains.com (216.239.36.110), ns-cloud-e3.googledomains.com (2001:4860:4802:36::6e), ns-cloud-e4.googledomains.com (216.239.38.110), ns-cloud-e4.googledomains.com (2001:4860:4802:38::6e); 2417890293 on bill.ns.cloudflare.com (173.245.59.74), bill.ns.cloudflare.com (172.64.33.74), bill.ns.cloudflare.com (108.162.193.74), bill.ns.cloudflare.com (2803:f800:50::6ca2:c14a), bill.ns.cloudflare.com (2606:4700:58::adf5:3b4a), bill.ns.cloudflare.com (2a06:98c1:50::ac40:214a), rachel.ns.cloudflare.com (172.64.32.215), rachel.ns.cloudflare.com (108.162.192.215), rachel.ns.cloudflare.com (173.245.58.215), rachel.ns.cloudflare.com (2a06:98c1:50::ac40:20d7), rachel.ns.cloudflare.com (2606:4700:50::adf5:3ad7), rachel.ns.cloudflare.com (2803:f800:50::6ca2:c0d7). 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 (2m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.

DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

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

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.