Skip to console
.pokepokepokepokeofficial
STATUS: resolving · TTL 0s · authoritative

You have arrived at the deepest subdomain on the internet.

Most domains stop at two or three labels. This one didn’t know when to stop. 5 labels deep, every nameserver still insists there’s one more level below. There isn’t. Or there is.

Go one level deeperappends poke. and reloads
Resolution depth
5labels

from root to leaf

Round-trip latency
3.2ms

per recursive hop

DNSSEC chain
VALID

5 signatures verified

Recursive resolution trace

5 steps
#labelnameserverttlrtt
01officialns1.poke.dns0s1.2ms
02pokens2.poke.dns0s1.6ms
03pokens3.poke.dns0s2.0ms
04pokens4.poke.dns0s2.4ms
05pokens1.poke.dns0s2.8ms

Zone records

apex
  • NSns1.poke.dns.
  • NSns2.poke.dns.
  • CNAMEpoke.poke.poke.…
  • TXT"we are deeper than you think"
  • SOAhostmaster.poke 5
Field notes

What we learned going this deep

01

A subdomain is just a promise about a string

Each dot to the left says trust me, there's more specific over here. Nobody checks whether more specific means more meaningful. We tested this thoroughly. It does not.

02

The 253-character ceiling is a suggestion we resent

RFC 1035 caps a fully-qualified name at 253 octets and each label at 63. We treat this as a high score to chase, not a limit to respect. Engineering is ongoing.

03

Every CNAME here points home

Follow any alias far enough and it resolves to the apex you started at. This is either elegant cache design or a stack overflow with good branding. We ship both.

04

TTL zero, because nothing should be remembered

Caching implies the answer stays true. At this depth the answer is true for exactly as long as it takes to read it, after which a poke is appended somewhere and the world shifts left.

Live console

Watch it resolve to itself

resolver · 5 hops
$dig +trace official.poke.poke.poke.poke.
>; 5 delegations followed
>; longest label run on record: 5
>official. 0 IN A 127.0.0.1
>;; answer is itself, recursion stable
@poke.poke.poke.poke.official
Resolution FAQ

Questions from the leaf node

Is this a real subdomain?

It's as real as any name resolution: a chain of strangers agreeing about a string. Whether that constitutes real is between you and your resolver.

Why does the path keep getting longer?

Because you keep going deeper. The Recursion Button appends one more poke label and reloads. The path navigator faithfully renders every level. Stop clicking and it stops growing.

Will I hit the 253-character limit?

Eventually the URL gets unwieldy long before any nameserver complains. We've capped the recursion at a polite ceiling so your browser doesn't file a grievance.

Can I go back up a level?

The internet was not designed with shame in mind, so yes: your back button ascends one delegation at a time. The dashboard pretends not to notice.