mapfan.com

Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: ns-201.awsdns-25.com, ns-772.awsdns-32.net. ns-1114.awsdns-11.org, ns-201.awsdns-25.com, ns-2042.awsdns-63.co.uk, ns-772.awsdns-32.net report NS ns-1114.awsdns-11.org ns-201.awsdns-25.com ns-2042.awsdns-63.co.uk ns-772.awsdns-32.net.

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). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 5m; resolvers may use either.

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: mail.mapfan.com

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

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

DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:infra_dev@geot.jp (needs mapfan.com._report._dmarc.geot.jp). Ask the report provider to publish the record, or check the address.

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.