Policy
HostWithShery uses public DNS, authoritative DNS, RDAP, TLS handshakes, HTTP responses, public network metadata and provider signatures.
- public DNS
- authoritative nameservers
- RDAP
- TLS certificates
- HTTP headers and HTML
- public ASN data
DNS and delegation
The service uses recursive DNS, authoritative nameserver queries and public record types such as A, AAAA, CNAME, MX, TXT, NS, SOA, CAA and DNSSEC delegation data. Propagation views use separately deployed regional probes rather than pretending that several resolvers on one server represent the world.
Web and TLS evidence
HTTP/HTTPS requests provide status, redirect chains, response headers, compression/cache signals and a limited page sample for placeholder, canonical, robots and technology checks. TLS handshakes provide certificate dates, SAN coverage, issuer/chain data, negotiated protocol and supported TLS-version evidence.
Registration and network metadata
RDAP is used for public domain registration/status events where a registry exposes them. Public IP-to-ASN information is used to identify the visible network. ASN or CDN ownership is not treated as proof of a hidden origin host.
Mail and crawler data
MX, SPF, DKIM, DMARC, BIMI, MTA-STS and TLS-RPT checks use public DNS and documented HTTPS policy locations. Crawler accessibility uses robots.txt, sitemap, canonical, meta robots and X-Robots-Tag evidence rather than attempting to predict search rankings.
Technical references
These primary standards and provider documents are used to verify the behavior described on this page. Provider dashboards can change, so use the current official value for tenant-specific DNS records rather than copying an example from another account.