vgchartz.com

Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: ns4.vgchartz.com. ns1.michonline.net, ns3.vgchartz.com, ns4.vgchartz.com report NS ns1.michonline.net ns3.vgchartz.com ns4.vgchartz.com.

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

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns3.vgchartz.com: "9.3.6-P1-RedHat-9.3.6-25.P1.el5_11.3"; ns4.vgchartz.com: "9.3.6-P1-RedHat-9.3.6-25.P1.el5_11.12". Hide or replace the version string.

SOA · refresh 5m is outside 20m–1d; retry 5m should be shorter than refresh 5m; negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 5m, retry 5m, expire 28d, negative TTL 1m.

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), NS (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1m; 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: mail.vgchartz.com

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

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.