virginmoneygiving.com

Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: ans3.virginmoney.com, ans4.virginmoney.com. ans1.virginmoney.com, ans2.virginmoney.com, ans3.virginmoney.com, ans4.virginmoney.com report NS ans1.virginmoney.com ans2.virginmoney.com ans3.virginmoney.com ans4.virginmoney.com.

Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

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

DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.

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: cluster3.eu.messagelabs.com, cluster3a.eu.messagelabs.com

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.