Your workflow currently sources resolvers from The Public DNS Server List as one of ten inputs. That source is powered by corny/dnscheck, which has been dormant for years — the community has flagged this repeatedly, and multiple projects (including this one) exist partly because the raw data can't be trusted.
publicdns.info is a separate, actively maintained project that probes 90,000+ resolvers every 72 hours and publishes ~8,500 confirmed-live servers with status indicators (OK, NX_HIJACK, TIMEOUT, BAD).
Suggestion: Add publicdns.info as an 11th source, or replace the stale public-dns.info entirely. A pre-validated resolver list is also available at publicdns-resolvers, updated daily via GitHub Actions.
Starting from a cleaner upstream would mean dnsvalidator has less noise to filter during your multi-round validation, potentially speeding up the workflow and improving the final output quality.
Your workflow currently sources resolvers from The Public DNS Server List as one of ten inputs. That source is powered by
corny/dnscheck, which has been dormant for years — the community has flagged this repeatedly, and multiple projects (including this one) exist partly because the raw data can't be trusted.publicdns.info is a separate, actively maintained project that probes 90,000+ resolvers every 72 hours and publishes ~8,500 confirmed-live servers with status indicators (OK, NX_HIJACK, TIMEOUT, BAD).
Suggestion: Add publicdns.info as an 11th source, or replace the stale public-dns.info entirely. A pre-validated resolver list is also available at publicdns-resolvers, updated daily via GitHub Actions.
Starting from a cleaner upstream would mean dnsvalidator has less noise to filter during your multi-round validation, potentially speeding up the workflow and improving the final output quality.