r7.com

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: asia1.akam.net: "48878.31"; eur5.akam.net: "48878.33"; ns1-228.akam.net: "41824.11"; ns1-228.akam.net: "41824.6"; ns1-95.akam.net: "41824.9"; ns1-95.akam.net: "41824.8"; usc3.akam.net: "48878.31"; use5.akam.net: "48878.29"; use5.akam.net: "48878.27"; use9.akam.net: "48878.32"; usw1.akam.net: "41824.5". Hide or replace the version string.

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 (1m), MX (1m). 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.

SPF · SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.

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.

MX · The following MX hosts could not be resolved to IPv6 addresses: mx1.r7.email.locaweb.com.br, inbound-smtp.us-east-1.amazonaws.com, mx2.r7.email.locaweb.com.br, mx3.r7.email.locaweb.com.br, mx4.r7.email.locaweb.com.br

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits), mail (1024 bits). Rotate to a 2048-bit key.

DKIM · These keys have t=y, so receivers treat DKIM failures as a test: mail. Remove t=y once DKIM works.

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.