Public Blank

Quick Start

1. Email root@public-common.com with the domain you want parked.
2. An nginx server block is added for your domain, and a TLS certificate is issued via Let's Encrypt (DNS-01).
3. You receive the IP addresses and DNS record instructions.
4. Set the A and AAAA records at your DNS provider.
5. Once DNS propagates, your domain serves the parking page over HTTPS.

DNS Setup

The host is single-node, dual-stack:

For your domain (e.g. example.com), the apex needs:

example.com.        IN  A     37.27.97.202
example.com.        IN  AAAA  2a01:4f9:3070:145b::1

If you want www to park here as well:

www.example.com.    IN  A     37.27.97.202
www.example.com.    IN  AAAA  2a01:4f9:3070:145b::1

If your registrar's UI uses record forms rather than zone-file syntax, the equivalent is: type A, host @, value 37.27.97.202; then type AAAA, host @, value 2a01:4f9:3070:145b::1.

Confirm propagation against any validating resolver — for example public-rdns.com:

dig @public-rdns.com +short example.com A
dig @public-rdns.com +short example.com AAAA

If you host authoritative DNS on public-adns.com, add the two records to your zone file and bump the serial.

Privacy

A parking page should do nothing interesting. We do not log individual page views. No visitor data is stored, sold, or shared with third parties.

• No access logging — page views are not written to disk.
• No analytics, no cookies, no third-party content — the parking page is static HTML.
• No ads, no monetisation — this exists so you do not have to host a parking page yourself.
• Encrypted storage — data at rest is protected with ZFS native encryption.
• No shell history — operator sessions leave no command history on the server.
• Headless server — no physical console exposed to the public internet.

How to Use

There is no self-service portal. To park a domain, email root@public-common.com with the FQDN. The operator adds an nginx server block, issues a certificate, and replies with the DNS values under DNS Setup.

To unpark a domain, change its DNS to point elsewhere. The parking record on this server can be removed on request.

Subdomains use the same flow — set A/AAAA on the subdomain and email the FQDN.

TLS

Each parked domain gets its own Let's Encrypt certificate, issued via ACME with the DNS-01 challenge and an ECC P-256 key. Certificates are managed centrally on the Public Consortium management host and synchronised to this host before nginx reloads.

• HTTPS is on by default, on TCP 443 (TLS).
• Plain HTTP on port 80 is also served. Use the https:// URL when you want TLS — there is no automatic redirect.
• HTTP/2 and HTTP/3 (QUIC) are enabled where the client supports them.
• Certificates auto-renew. There is nothing for you to do.

Features

• HTTPS with HTTP/2 and HTTP/3
• IPv4 and IPv6
• Per-domain Let's Encrypt certificates (ECC P-256), auto-renewed
• Hardened response headers: X-Content-Type-Options: nosniff, X-Frame-Options: DENY
• HTTP GET only — every other method is denied at the web tier
• Static HTML, no scripts, no third-party assets
• No charge, no signup, no API key

Infrastructure

• OS: FreeBSD
• Web server: nginx with HTTP/2 and HTTP/3
• Filesystem: ZFS with native encryption
• Certificates: issued centrally on root.public-common.com via acme.sh, synced to this host with rsync
• nginx layout: one server block per parked domain, each pinned to its own certificate

Troubleshooting

The browser shows a certificate warning

Most often the DNS is pointed here but the certificate has not been issued for that name yet. Issuance happens on the next ACME loop after the request — wait a few minutes and reload, or email to confirm.

The page loads from one network but not another

Usually your AAAA record is set but the client is reaching us over a broken IPv6 path (or vice versa). Check both dig A and dig AAAA for your domain, and confirm both addresses match DNS Setup.

I see a different site at the IP

The host serves many domains from the same IP — nginx routes by SNI / Host header. Reaching the IP directly without an SNI returns a default response, not your domain. That is normal.

My old hosting still shows up

DNS caches. Wait for your previous record's TTL to expire, or flush the resolver you are testing from.

FAQ

Acceptable Use

• Park your own domains, not domains you do not control.
• Do not use the parking page as part of a phishing or malware infrastructure. Such domains are removed without notice and reported.
• Do not try to wrap arbitrary content through the parking host — the page is static and there is nothing to wrap.
• Abusive sources may be rate limited or blocked without notice.

Other Projects