theip.io · powered by TheyCloud TAP

Claim an IP.
Point it at TAP.

theip.io is a hostname registry for TheyCloud TAP. Pick any IPv4-looking address — 85.30.41.40.theip.io — claim it, and bind it to one of your TAP slugs. First come, first served. One IP, one owner.

$ ssh root@85.30.41.40.theip.io
Pick an IPv4 address to claim
Checking availability…
Bind it to a TAP slug you own
once claimed, resolves
you'll type
ssh root@203.0.113.42.theip.io
TAP routes to
ssh root+webserver@webserver.myproject.tap.theycloud.com
What it is

A hostname you claim, not one you're assigned

TheyCloud TAP gives private infrastructure named public endpoints — like webserver.myproject.tap.theycloud.com. theip.io adds a registry on top: pick any IPv4-looking address, claim it, and tell it which TAP slug to resolve to.

Each address can only be reserved once. Whoever claims 85.30.41.40.theip.io first owns it — and decides where it points. You can repoint it to a different slug you own at any time, or release it back to the pool.

No new client software. No configuration on the connecting end. Once claimed, it works with every tool that speaks DNS.

How it works · setup

Claim it once. It's yours.

Reserving an address is a one-time step. Pick an IP, pick the TAP slug it should point to, and the binding is permanent until you change it.

1Check availability
85.30.41.40.theip.io unclaimed
2Claim it
Reserve 85.30.41.40 under your TheyCloud account — no one else can take it
3Bind a slug
85.30.41.40.theip.io webserver.myproject.tap.theycloud.com
4It's live
Resolvable immediately. Repoint or release it anytime from your dashboard.
Hostname format
85.30.41.40.theip.io
85.30.41.40

Any IPv4-looking address you've claimed — doesn't need to be a real or routable IP

theip.io

The registry domain — resolves to whichever TAP slug you bound it to

How it works · every time after

Then it's just a connection

Once bound, the address behaves like any other hostname. No re-claiming, no re-resolving — the binding holds until you change it.

1You connect
$ ssh root@85.30.41.40.theip.io
2DNS resolves
85.30.41.40 your binding webserver.myproject.tap.theycloud.com
3TAP routes
root+webserver @ shared TAP gateway :22 10.0.1.10 (private VPC)
4You're in
Welcome to Ubuntu 22.04 LTS (GNU/Linux 5.15.0)
Every protocol, same pattern

Native ports, no exceptions

Whatever's listening on the other end, theip.io keeps the standard port. No remapping, no protocol-specific tunnel.

Protocol
Connection string
Port
SSH
ssh root@85.30.41.40.theip.io
22
HTTPS
https://85.30.41.40.theip.io
443
MySQL
mysql -h 85.30.41.40.theip.io -u root -p
3306
Redis
redis-cli -h 85.30.41.40.theip.io
6379
Reservation rules

One IP. One owner. No squatting loopholes.

theip.io is a registry, not a free-for-all. A small set of rules keeps every address unambiguous.

First come, first served
  • Any IPv4-looking address can be claimed
  • Available the instant it's not reserved
  • No waitlists or auctions
Exclusive while reserved
  • Only the claiming account can bind it
  • No one else can take it from you
  • Visible only as taken to others — never whose
Yours to manage
  • Repoint to a different TAP slug anytime
  • Release it back to the pool when done
  • Released IPs become claimable again immediately
Part of TheyCloud TAP

theip.io is a TAP feature

theip.io doesn't replace TAP — it's a registry on top of it. TAP handles the gateway, routing, DNS, and SSL. theip.io lets you claim a short address and decide for yourself where it points.

TAP handles
  • Gateway routing
  • Protocol-aware forwarding
  • Auto DNS & SSL
  • VPC integration
  • Standard port mapping
theip.io adds
  • Claimable IPv4 hostnames
  • One owner per address
  • You choose the bound slug
  • Repoint or release anytime
  • Same standard ports
You get
  • Native SSH on :22
  • HTTPS on :443
  • DB on native ports
  • No VPN client
  • No tunnel software
FAQ

Common questions

Do I need a TAP account to claim an address?

+
Yes. theip.io is a registry layer for TheyCloud TAP. You'll need at least one TAP slug to bind the address to — claiming an IP on its own doesn't do anything until you point it somewhere.

Does the IP I claim need to be real?

+
No. The address just needs to look like an IPv4 address (four dot-separated numbers, 0–255) — it doesn't need to be a real, public, or routable IP. Most people pick something memorable rather than their actual server's address.

What happens if the IP I want is already taken?

+
You'll see it marked as reserved and won't be able to claim it. theip.io doesn't show who holds an address, only whether it's available — try a different one, or wait for it to be released.

Can I repoint my IP to a different TAP slug later?

+
Yes. You keep the address as long as you hold it; the slug it's bound to can be changed anytime from your dashboard. The hostname stays the same — only where it routes changes.

What happens to my reservation if I close my TAP account?

+
The address is released back to the available pool and can be claimed by someone else. If you plan to come back, release slugs you're not using instead of letting the whole account lapse.

Can I use theip.io in scripts and CI pipelines?

+
Yes — once bound, it's plain DNS, so anything that opens a socket works: ssh, curl, database clients, deploy scripts, monitoring agents. No SDK or wrapper required.
Ready when you are

Pick an IP. Make it yours.

Unclaimed addresses are available right now — first come, first served.

$ ssh root@85.30.41.40.theip.io