yellowpages.com

Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns1.thryvinc-ns.com (glue 198.41.222.155, zone 198.41.222.155, 2400:cb00:2049:1::c629:de9b); ns2.thryvinc-ns.com (glue 162.159.10.178, zone 162.159.10.178, 2400:cb00:2049:1::a29f:ab2); ns3.thryvinc-ns.com (glue 162.159.11.220, zone 162.159.11.220, 2400:cb00:2049:1::a29f:bdc). Update the glue at your registrar.

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.thryvinc-ns.com: "2026.10.2"; ns2.thryvinc-ns.com: "2026.10.2"; ns3.thryvinc-ns.com: "2026.10.2". Hide or replace the version string.

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.

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: yellowpages-com.mail.protection.outlook.com, yellowpages-com.mail.protection.outlook.com

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

MX · The PTR name of these addresses does not resolve back to the same address: 52.101.60.65 -> mail-bn3pr02cu00101.inbound.protection.outlook.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.