Troubleshooting
Website verification keeps failing
The check looks for your exact token in a DNS TXT record at _slopsquash.<host>, in a meta tag on the home page, or in the well-known file, six tries per ten minutes.
Updated
How the check runs
Verify looks up the TXT records for _slopsquash.<your-host>, then fetches the site's home page and looks for the meta tag, then fetches /.well-known/slopsquash-verification.txt. It stops at the first place it finds the token. Failures show the reason on the verification panel. You get six attempts per ten minutes per website.
DNS record
- The record name is
_slopsquash.example.comforexample.com(many DNS editors want just_slopsquashin the name field). The value is the token exactly as shown, including theslopsquash-site-verification=prefix. - DNS changes take time to propagate; wait a few minutes and try again. On Cloudflare the change is usually immediate; the panel's Open Cloudflare DNS link takes you to the right zone.
- Verifying
www.example.comchecks_slopsquash.www.example.com? No: the check uses the host you entered, so enter the host the way you want it recorded and put the record under it.
Meta tag
- It must be in the
<head>of the page at the URL you entered (the home page), served over the same protocol. A tag on a subpage is not found. - Copy it verbatim from the panel. Frameworks that strip unknown meta tags, and caches that serve an old version of the page, are the usual causes.
Well-known file
- Plain text at
/.well-known/slopsquash-verification.txton the host you entered, containing the token. Some hosts need the.well-knowndirectory created explicitly or block dotted directories; check the file loads in a browser first.
"Verified by another account"
A domain can be verified by one Slop Squash account at a time. See A channel is already verified on another account.
Still failing
Email creators@slopsquash.com with the host and the method you used. Keep the record, tag or file in place after verification; we re-check from time to time.