Bot intelligence record

Termly

Review first

Use the TermlyBot identifier to separate Termly security scanning or verification traffic from normal visitor requests in server logs.

Security Security Verified Bot Confidence: Medium Verified: Yes robots.txt: No

User-Agent Pattern

Termly
TermlyBot

Robots.txt Snippet

Copy-ready
User-agent: TermlyBot Disallow: /

Handling Guidance

Depends

Use this record as bot intelligence, then verify the request source and behavior before allowing, blocking, or rate limiting.

Security scanning, malware checks, abuse prevention, compliance review, or vulnerability monitoring.

Record Details

Structured data
Operator
Termly
Family
Termly
Type
Security
Purpose
Security
Identity type
Verified Bot
Confidence
Medium
Last verified
2026-04-01
Last checked
2026-05-20
Source type
Verified Directory
Spoofing risk
User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.

Notes

Termly is listed in the Botcrawl directory as a security scanner from Termly. The primary identifier for log review is TermlyBot.

Identification

  • User-agent pattern: TermlyBot
  • Family: Termly
  • Type: Security
  • Kind: Scanner

Common use

Security scanning, malware checks, abuse prevention, compliance review, or vulnerability monitoring.

Verification and handling

Confirm the user-agent against server logs and use published operator documentation, IP ranges, reverse DNS, or other trust signals when available.

Directory guidance marks the risk level as Neutral and the blocking decision as Depends. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.

Robots.txt handling: No.

Evidence and Source

  • Validate the identifying user-agent or signature against the operator documentation before creating hard allow rules.
  • Match `TermlyBot` as a case-insensitive substring in HTTP user-agent logs. Review bot_aliases for alternate names or product labels. Use bot_http_agent for full user-agent examples when the client sends a longer browser-like string. Do not treat a user-agent match alone as proof of identity for allow-listing.
  • Security scanning, malware checks, abuse prevention, compliance review, or vulnerability monitoring.
  • User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.

WordPress Bot Protection

Bot Blocker for WordPress

Monitor bot traffic, review live activity, and control AI crawlers, scrapers, scanners, spam bots, and fake trusted bots from one clean WordPress dashboard.