Scope

and.guide covers DNS, custom domains, HTTPS and certificates, and the operation of public hostnames. A guide has to answer a concrete question inside that scope — a decision, a failure, or a procedure. We do not publish news, product announcements, or general technology commentary.

Evidence: what we run and how we show it

  • Observed output is real. Anything presented as the result of a command was produced by running that command, on the date shown as Last tested. We never edit values in captured output. When we shorten it, we mark the cut.
  • Examples are labeled as examples. Configuration you are meant to adapt uses reserved names and addresses (example.com, 192.0.2.0/24, 2001:db8::/32) and is never presented as something we observed.
  • No invented experience. We do not describe incidents, customers, or projects that did not happen. Hypothetical scenarios are written as hypotheticals.
  • Light-touch testing. We query public infrastructure the way any user would. We do not scan third-party networks or publish names that look vulnerable.

Sources

Product-specific behavior is checked against the vendor's current documentation. Protocol behavior is checked against RFCs and other standards documents. Secondary sources — forum posts, blog articles, videos — can point us to a question but are not cited as authority. Every guide lists the sources it was checked against, so readers can confirm details that may have changed since.

Use of AI tools

We use AI writing assistants for research, outlining, drafting, and editing. We do not publish unreviewed AI output as a guide. The rules above apply regardless of how a sentence was first drafted: commands are run for real, claims are checked against primary sources, and a guide is reviewed before publication. 1990Company is responsible for every published claim.

Dates and updates

  • Published is the date a guide first appeared.
  • Updated changes only for material revisions — new or corrected instructions, not typo fixes.
  • Last tested is the date of the most recent live run of the commands shown in the guide.

We revisit a guide when a platform changes its documented setup, when a standard is revised, or when a reader reports a mismatch.

Corrections

Send corrections to admin@and.guide with the page URL, the claim you believe is wrong, and a source if you have one. We check every report. If the report is right, we fix the guide and update its date; if a correction changes a recommendation, the guide says what changed.

Advertising and independence

The site is supported by display advertising from Google AdSense. Advertisers cannot buy coverage, placement, or conclusions. We do not accept sponsored posts or payment for reviews, and we do not use affiliate links. Topic choices and recommendations are made on the basis of reader questions, testing, and sources only.

Relationship to the subdomain service

1990Company also adds DNS records for a small number of manually reviewed project subdomains under and.guide, pointing each name at a site its owner hosts elsewhere. Guides do not promote that service, and requests have no influence on what the guides recommend.