A drop-in replacement of Node's 'dns' module using 'fetch' and DNS-over-HTTPS
the http/https agent used by the npm cli
Fetch DNS over HTTPS
A decorator on top of `fetch` that caches the DNS query of the `hostname` of the passed URL
Fetch DNS info.
A decorator on top of `fetch` that caches the DNS query of the `hostname` of the passed URL
Opinionated, caching, retrying fetch client
Opinionated `fetch` optimized for use inside microservices
An abstract-encoding compliant module for encoding / decoding DNS packets
Opinionated `fetch` optimized for use inside microservices
Compare DNS record strings for equality
DNS over HTTP resolver
OpenTelemetry instrumentation for `node:dns` name resolution module
Low level multicast-dns implementation in pure javascript
Encode/decode DNS-SD TXT record RDATA fields
Discover publicly available DNS Records for a domain
Make low-level DNS requests with retry and timeout support.
Parse and stringify mdns service types
Middleware to set X-DNS-Prefetch-Control header.
TypeScript definitions for dns-packet
Abstraction for exponential and custom retry strategies for failed operations.
A light-weight module that brings Fetch API to node.js
Resolve DNS queries with browser fallback
An implementation to speed up the nodejs `dns.lookup` method by avoiding thread pool and using tangerine library
Allows capistrano to configure deploy hosts and roles using DNS SRV records
HAST stands for 'Hosting Account Status Tool'. HAST is a tool for fetching domains from Apache configuration files and from Postfix on a hosting server environment. It will then run a report, checking the DNS records for each domain to see if they match your server. This is important for finding "dead" domains where the domain either doesn't exist anymore or where the owner have moved it to another hosting provider. Before you can use HAST, you need to setup a config.yml file. Run 'hast --generate-config > config.yml' to create a sample config file that you can modify.
Instead having a complex data schema to assign record sets to DNS zones, dns_one assigns one or a few record sets to many zones. Configure your record sets in YML files and fetch your domains from a database or YML backend.
Scrapetor is a Ruby HTML parsing + scraping toolkit. The parser is a native C arena DOM with structural indexes built at parse time and NEON SIMD scanners in the SAX hot loop. A streaming extraction engine compiles the schema DSL into a single forward pass — no DOM materialised, one Ruby boundary crossing per document. On builds where libcurl is available, Scrapetor::Fetcher adds an HTTP/2-capable fetch layer with per-thread connection cache, shared DNS + TLS session pool, in-process gzip / deflate / brotli / zstd decoding, iconv charset transcoding, retry + exponential backoff, ETag / Last-Modified disk cache with bulk revalidation, per-host throttle, cookie jar, basic + bearer auth, proxy, and three bulk concurrency models (parallel_fetch / multi_fetch / streaming multi_each). Scrapetor::Session ties the cookie / auth / throttle / retry policies together. Also ships robots.txt + sitemap.xml parsers, a bounded-memory streaming HTML parser, and structured-data extractors (JSON-LD, OpenGraph, Schema.org, Microdata, RDFa, Twitter Cards). The Net::HTTP-based Scrapetor.fetch is preserved as the no-libcurl fallback.