trendhunter.com

Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com; only in the zone: ns-1522.awsdns-62.org, ns-1848.awsdns-39.co.uk, ns-32.awsdns-04.com, ns-663.awsdns-18.net. ns-1522.awsdns-62.org, ns-1848.awsdns-39.co.uk, ns-32.awsdns-04.com, ns-663.awsdns-18.net, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com report NS ns-1522.awsdns-62.org ns-1848.awsdns-39.co.uk ns-32.awsdns-04.com ns-663.awsdns-18.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.

DNSSEC · The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.

MX · Found 7 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.

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

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.