Overview
Meltwater is a monitoring bot used for uptime monitoring, synthetic checks, performance measurement, accessibility review, and site-health testing.
Its primary user-agent pattern is Meltwater; related patterns include Meltwater crawler.
Meltwater is Unverified at the identity-evidence level. The listed identity remains useful for detection, but this record does not currently contain authoritative evidence sufficient to authenticate the identity claim.
Meltwater is marked as respecting robots.txt directives for crawler access control.
Meltwater should be reviewed against site policy, source evidence, crawl rate, and requested paths before a permanent allow or block rule is created.
Identity
- User-Agent Pattern
-
Meltwater - Aliases
- Meltwater crawler
- HTTP Agent Examples
-
Meltwater - Robots Token
- Meltwater
- Identity Type
- Observed
- Evidence Method
- Treat `Meltwater` as an identity signal only. Confirm it with current operator documentation, cryptographic verification, forward-confirmed reverse DNS, source-network ownership, or other authoritative evidence before trusting the claimed identity.
Classification
- Type
- Monitoring
- Kind
- Monitor
- Family
- Meltwater
- Purpose
- Monitoring
Behavior and handling
- Common Use
- Meltwater is used for uptime monitoring, synthetic checks, performance measurement, accessibility review, and site-health testing.
- Detection Notes
- Meltwater traffic is primarily detected by the `Meltwater` user-agent pattern; related patterns include `Meltwater crawler`. Compare source IPs, reverse DNS, request paths, and crawl cadence before trusting the traffic.
- Respects robots.txt
- Yes
- Spoofing Risk
- Meltwater has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
- Risk
- Neutral
- Recommended Handling
- Depends
Rules and controls
- Robots.txt Snippet
-
User-agent: Meltwater Disallow: /
Relationships
- Operator
- Meltwater Checked 2026-08-07
Relationships without an Evidence link are normalized from the canonical directory record. They should not be interpreted as independent proof of physical presence or request origin.