Konto, Team & Sicherheit
Verify a domain with a DNS TXT record
Prove that you control a domain by adding a fastping-verify TXT record, so FastPing can run security exposure scans against it.
Security scans request sensitive paths such as /.env and /.git/config. Running that against someone else's website would be a probe of their systems, so FastPing only scans domains whose ownership your organisation has proven. Other monitor types do not need verification.
- Open Verified domains in the dashboard and add the domain, for example
example.com. - FastPing shows a TXT record with a value such as
fastping-verify=Qm9x…. At your DNS provider, add a TXT record on the domain itself with exactly that value. In most DNS panels the name for the domain itself is@or left empty.DNS recordsexample.com. TXT "fastping-verify=Qm9x…" - Click Verify. FastPing looks the record up through public resolvers (Cloudflare and Google).
Verification applies to exactly the name you added: to scan www.example.com as well, add and verify it too (its TXT record goes on www). The TXT record does not interfere with SPF or other TXT records on the same name, and you can leave it in place.
| Message | What it means | What to do |
|---|---|---|
TXT record not found yet. DNS changes can take a few minutes to appear. | The resolvers do not return the record (yet). | Check that the record is on the right name and the value matches exactly, without extra quotes or spaces, then wait for the DNS provider to publish it. |
Too many requests. Try again in 60 seconds. | Verification attempts are limited to 30 per 10 minutes per organisation. | Wait, then try again. |
The DNS lookup shows the TXT records the public resolvers currently return for a name.
Removing a verified domain pauses the security scan monitors that use it. An organisation can add up to 200 domains.