Detectify Validation Specification

For us to be able to scan your domain, you need to specify an authorization token and attach it to your domain. You’ll receive one such token when you’re trying to add a new domain from the Detectify dashboard. The token will always be a string consisting of 32 hexadecimal characters unless you’re authenticating using Google Analytics where we instead will use your UA-token as provided by Google.

We have a variety of ways of authorizing domains to be scanned and the authorization methods are listed below.

Meta verification

You may create a HTML meta tag, and add it to the head part of your index page like so:

<meta name="detectify-verification" content="0123456789abcdef0123456789abcdef">

Any attempt to put it outside of <head> will be disqualified by our validation routine.

File verification

A file may be added to your web root with the name set to the token, the extension set to “txt”, the MIME-type set to “text/plain” and the content set to “detectify”, like so:

http://example.com/0123456789abcdef0123456789abcdef.txt

DNS CNAME verification

If you only have access to the domain name (or if you like to keep your code intact), you may add a CNAME alias on your domain. The sub domain will be detectify followed by the token, and it must point to verification.detectify.com. Like so:

;; ANSWER SECTION:
detectify0123456789abcdef0123456789abcdef.example.com.  86390   IN  CNAME   verification.detectify.com.

DNS TXT verification

An option to the CNAME is the DNS TXT record. If must be specified like so:

;; ANSWER SECTION:
example.com.        3600    IN  TXT "detectify-verification=0123456789abcdef0123456789abcdef"

Google Analytics verification

You may let us get temporary access to your Google Analytics account. That way we can verify that you’re a valid administrator of the domain. By doing so you wont have to make any new changes whatsoever, we’ll keep a notice of the current UA token on your domain and use that for further authentication.

Detectify validation