vmware.com

Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns95.ultradns2.com, ns95.ultradns2.org; only in the zone: ns96.ultradns2.com, ns96.ultradns2.org. edns161.ultradns.biz, edns161.ultradns.com, edns161.ultradns.net, edns161.ultradns.org, ns95.ultradns2.com, ns95.ultradns2.org, ns96.ultradns2.com, ns96.ultradns2.org report NS edns161.ultradns.biz edns161.ultradns.com edns161.ultradns.net edns161.ultradns.org ns96.ultradns2.com ns96.ultradns2.org.

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 (2m30s). 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.

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

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

DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector2 (1024 bits), mx (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.