About

What this is

A small WireGuard server, hand-run by one person, intended for friends and family. You connect a phone or laptop, and your traffic exits the public internet from this address instead of from your local cafe wifi or hotel ISP. Sites you visit see this server's IP, not yours. DNS lookups go through this server too.

What this isn't

• It's not a commercial product. There's no billing, support tier, or SLA.
• It's not a "no-logs audited" provider in the marketing sense. It's run on small equipment by one person whose word and shell history is the only audit you get. Treat it accordingly.
• It's not enough to make you anonymous. A VPN swaps one observer (your ISP) for another (this operator). It does not hide you from the sites you log into, browser fingerprinting, or anyone able to inspect your device.
• It's not a tool to make illegal activity safe.

What it's good for

• Hostile public networks (hotel wifi, conferences, airports).
• Avoiding your ISP's per-site visibility into your browsing.
• A stable IP on the open internet for accessing services that allowlist specific addresses.
• Routing around a country-block or a geo-fenced page (technically possible, sometimes against the destination site's ToS — your call).

The architecture, in two lines

WireGuard server runs on a desktop on a residential symmetric fiber link. Peers connect inbound to vpn.domainless.fun:51820; outbound traffic is masqueraded out via the desktop's public IP. The same hostname's secondary record points at a BuyVM Las Vegas VPS for capacity / failover; whether that secondary is active depends on how recently the operator has set it up.

Open-source you can audit yourself

WireGuard kernel module: wireguard.com. Server config templates and the small Express service that powers this status page are part of the J&G Studios codebase.