How domain verification works on Internet Map

Handles are unique. Trust is not automatic. Domain verification is how Internet Map connects a square to a website you control so visitors aren’t left guessing whether /@acme is Acme the company or Acme the fan account. This guide covers motivations, the flow, failure modes, and how verification interacts with Early badges and plan tiers.

Why verification exists

As soon as a public namespace gets interesting, impersonation appears. Verification doesn’t stop someone from claiming a weird adjacent handle, but it makes the real property obvious in the inspector and on the profile. Directories, leaderboards, and serious buyers all read “Verified” faster than a paragraph of explanation.

What verification is not

• Not a legal trademark registration.
• Not a Google Search ranking boost by itself.
• Not required to keep an Early badge.
• Not a KYC identity check of a human - it’s domain control.

The verification flow

From your dashboard or profile tools, start verification on the square. You’ll prove control of the domain attached to the claim - typically via a meta tag on the homepage or a DNS-style challenge, depending on the current product flow. When the check passes, the square status/badge updates to Verified and stays visible on the map panel and public page.

Troubleshooting

• Cached homepage - purge CDN cache after adding a meta tag.
• www vs apex mismatch - verify the exact host you claimed.
• Staging site - don’t point verification at a passworded preview.
• Multiple squares - verify each domain you care about; don’t assume one check covers all.
• DNS TTL - allow time for records to propagate before retrying.

Brand-safety tips while the map is young

Claim your exact brand handle early. Verify quickly. If you’re a trademark holder dealing with a confusing lookalike, document your verified square URL in public channels. Product support can help with clear abuse cases; verification gives everyone a shared source of truth.

FAQ

Can I verify before claiming?

You claim first, then verify. The square needs to exist as the object that receives the badge.

Does Startup require verification?

Verification is available as a trust feature across live squares - use it whenever you can edit the domain. Higher plans emphasize professional presence; verification is how that presence stays credible.