Domain verification stays pending
You have started the domain verification for your API key, but the status does not change. Here is how SilentShield checks your domain and why it may not find your DNS record or meta tag.
How SilentShield checks
SilentShield checks all pending verifications every 5 minutes, and immediately when you click “Check Status”. If the check finds nothing, the status simply stays “Pending”; there is no separate error message. As soon as the DNS record or meta tag is found, the domain counts as verified.
Causes
You started the verification again
Every start creates a new token and discards the previous one, including when you switch method. A record or tag with the old token no longer counts. Always use the value the dashboard currently shows.
The TXT record is on the wrong host
SilentShield looks up the TXT record on exactly the domain entered for the key: for www.example.com on www, for example.com on the domain itself (often @ in DNS interfaces). A record on a subdomain such as _silentshield is not read. If the host is a CNAME, it cannot carry a TXT record; use the meta tag instead.
The record value is not exact
The value must read exactly silentshield-verify= followed by the token, without spaces or additional text in the same record. Other TXT records on the same host do not interfere.
DNS has not caught up yet
Each check queries DNS afresh. Until the new record is visible to public resolvers, the check finds nothing; how long that takes depends on your DNS provider and the TTL. Use the commands below to see whether the record is visible from outside.
The meta tag is not in the delivered HTML
For the meta tag method, SilentShield fetches only the start page of your domain over HTTPS and reads the HTML your server delivers; no JavaScript runs. A tag inserted by a tag manager, a consent tool or a script is not found, nor is a tag that only exists on a subpage. After a change, clear the page cache.
The start page does not answer the check
The request waits at most 5 seconds, follows at most 3 redirects and reads only the first 512 KB, so place the tag near the top of the <head>. Maintenance mode, password protection or a bot protection that shows a challenge page instead of your page also hide the tag.
The status shows “Failed”
“Failed” instead of “Pending” has two causes: another account has already verified the domain, in which case please contact support; or the re-check after 30 days no longer found your record or tag. Restore it and start the verification again.
Checking from outside
Replace example.com with your domain:
dig +short TXT example.com
nslookup -type=TXT example.com
curl -s https://example.com/ | grep -o '<meta name="silentshield-verify"[^>]*>'The two methods step by step: Domain Verification