Who runs the site
and.guide is published by 1990Company, based in South Korea. We write and maintain every guide and tool on the site, and we run the domain ourselves: the site is served from Cloudflare Pages with DNS on Cloudflare, and we publish a teardown of that setup so you can see what our own configuration looks like from the outside, including the parts we would still change.
The library currently holds 29 guides and 4 browser tools. The guides are written in English and focus on DNS records and resolution, custom domains on hosting platforms, HTTPS and certificates, and the day-to-day work of keeping public hostnames healthy.
How we test
29 guides include command output captured from live systems. When a guide shows a dig,
curl, or openssl result, that result came from a real run on the date shown as
Last tested at the top of the guide. Dates are given in UTC. We use real public infrastructure for these captures — our own
domain, the published endpoints of hosting platforms, and well-known public sites — and we paste output as it was
returned. When lines are cut for length, the cut is marked.
- Location: South Korea. Anycast and CDN-backed names can return different addresses elsewhere in the world, so your output may differ in the details.
- Machine: macOS 26 workstation.
- Tools: DiG 9.10.6, curl 8.7.1, OpenSSL 3.6.3.
- Resolvers: the ISP-assigned default resolver, Cloudflare 1.1.1.1, Google Public DNS 8.8.8.8.
Configuration examples that you are meant to adapt use reserved documentation names and addresses such as
example.com and 203.0.113.0/24, so a copied example can never point at someone else's server.
Those examples are clearly configuration, never presented as observed output.
A guide is re-tested when a platform changes its documented setup or when a reader reports that something no longer matches. The Last tested date always reflects the most recent run.
How we write
Every guide starts from a specific question a reader has — which record to use, why an answer differs, what an error means — rather than a keyword. Platform behavior is checked against the vendor's current documentation, and protocol behavior against the relevant RFC. Those sources are listed at the end of each guide so you can check them yourself.
We use AI writing tools to help research, draft, and edit. They do not replace testing or source checking: commands are run for real, vendor claims are checked against primary documentation, and a guide is reviewed before it is published or updated. The full rules are in our editorial policy.
How the site is funded
and.guide shows ads served by Google AdSense on guide and tool pages. Advertisers have no say in what we write, we do not publish sponsored posts, and we do not use affiliate links. When we recommend a product or a setting, it is because the guide's testing and sources support it. Details on cookies and ad personalization are in the privacy policy.
Subdomain requests
We also accept a small number of requests for project subdomains under and.guide. The service is DNS only: after a manual
review we add a record to our Cloudflare zone that points a name such as yourproject.and.guide at a site you
host yourself, and your platform takes care of hosting and HTTPS. It is separate from the guides and does not influence
them. Details are on the subdomain requests page.
Contact
Corrections, questions, and suggestions for new guides are welcome at admin@and.guide. For a correction, include the page URL, the claim, and a source if you have one. More on the contact page.