HANDSHAKRClaim your passport

What can a buying agent confirm about you?

Enter your website. We read what a buying agent could read there and on Handshakr, and tell you what each thing means. Facts, not a score.

Six checks, each reported as a fact

Does the site answer over HTTPS?

We request your home page over HTTPS and note what answers, following redirects. If nothing does, we try plain HTTP once. A page served over HTTPS reaches the reader as you published it. Over plain HTTP it can be altered on the way.

Is there a Handshakr proof file?

We fetch /.well-known/handshakr.json, check it is JSON, and look up the handshakr_id it names among published Handshakr passports. Only whoever controls your domain can put a file there, so it is how your site says which passport is its own.

Does the home page carry Organization markup?

We look for schema.org Organization JSON-LD in the HTML your server sends, and note whether it fills in name, url, legalName and identifier. We report what is there, not what it says. Structured markup states who runs the site in a form software can read without guessing from the design.

What does robots.txt tell AI crawlers?

We read /robots.txt and work out, as the standard does, what it asks of GPTBot, ClaudeBot, PerplexityBot and Google-Extended. It is a request, not a lock. Blocking these crawlers is a legitimate choice; the result tells you what you are currently asking.

Is there an /llms.txt?

We check whether a file answers at /llms.txt, and whether it is a text file rather than your normal page. A proposed, optional convention for a plain-text guide written for language models.

Is there a published Handshakr passport for this domain?

We look for a published, public passport whose website is your domain. If there is one: whether it is claimed, how many public claims it carries and how many are verified and in date or backed by evidence, and whether agent access is switched on. A passport is what a buying agent reads about you on Handshakr. Agents may read a published passport; they may act on it only if the company has claimed it and switched agent access on.

What this does not check

• How any AI assistant ranks or recommends you. We cannot see inside them, so we do not report on it, and this is not a score of it.

• Handshakr does not sell ranking. Paying changes what you can do, never whether you appear or where. Commercial tier is not an input to matching and it is not a filter on discovery.

• Whether what your site says is true. The check reports that markup is there, not that its facts are right.

• Markup or files that only appear after JavaScript runs. We read the HTML your server sends.

• The Handshakr snippet in your page HTML, the other way to prove your domain. Your dashboard checks both.

• Crawlers other than the four named, or what any operator does with what it reads.

Results are not saved. We keep the domain you checked and a code for each check's outcome, and nothing about who ran it. To stop the tool being used to flood other people's sites, checks are limited to a few a minute from each network address, counted by the same short-lived limiter every public Handshakr endpoint uses.