🤖 Overview

pcore-http is a legitimate web crawler operated by the German cybersecurity and infrastructure monitoring company P-Core GmbH, based in Berlin. Its primary purpose is to perform automated HTTP-based health checks, performance benchmarks, and security posture assessments for websites enrolled in P-Core’s commercial monitoring platform. The data collected feeds into P-Core’s dashboard, which provides uptime tracking, response-time analysis, and vulnerability scanning (non-exploitative) for subscribing customers. According to the official P-Core documentation, the bot operates under strict ethical guidelines and is explicitly excluded from any form of content scraping or AI-training purposes.

🌐 Technical Behavior

The bot exhibits a systematic, interval-based crawl pattern, typically sending a single HTTP GET request to a monitored URL every 60 seconds by default (configurable by the customer). It uses the HTTPS protocol exclusively and supports HTTP/2 and TLS 1.3. The requesting IP ranges are publicly documented on the P-Core support page and fall under the ASN AS16276 (OVH) and ASN AS51167 (Contabo), with a dynamic allocation of about 50 distinct IPv4 addresses as of March 2025. The crawler does not follow redirects more than one hop and does not parse or crawl linked resources—it only verifies the availability and integrity of the exact target URL. User-Agent rotation is employed to avoid over-identification, but the string always contains the pcore-http token. The maximum request rate per IP is capped at 5 requests per second internally.

📋 robots.txt Compliance

P-Core officially states on their website (docs.pcore.io/bot) that pcore-http fully honors robots.txt directives as per the Robots Exclusion Protocol, including wildcard patterns and Disallow entirely. The bot reads the robots.txt file at the beginning of each monitoring session and caches it for up to 24 hours. If a URL is disallowed, the bot immediately skips the request and logs a “blocked by robots” event in the customer dashboard. There are no known incidents of non-compliance, and the bot’s behavior is independently verifiable via web server logs.

🔍 Detection Indicators

The primary User-Agent string is pcore-http/1.0 (with minor version variations like 1.1, 2.0), often appended with a platform identifier such as (+https://pcore.io/bot). A secondary header, X-Pcore-HealthCheck: true, is included in every request. The bot also sends a From header containing a contact email (e.g., [email protected]). Behavioral fingerprints include a consistent 60-second inter-request interval and a strict absence of any JavaScript rendering or cookie persistence. The bot never sends a POST or PUT request—only GET and HEAD.

📊 Data Usage

Collected data is used exclusively for the benefit of the website owner: uptime logs, latency metrics, SSL certificate expiry dates, and HTTP status code history. P-Core does not share or sell the data; it is processed within their closed monitoring environment and retained for a maximum of 90 days per the company’s privacy policy. No AI training, ranking algorithm, or third-party indexing occurs. The data serves real-time alerting and historical reporting for the customer’s own operational purposes.

⚙️ Rate Limiting Policy

Although pcore-http is legitimate and low-frequency (one request per 60 seconds per monitored URL), it may be rate-limited by defensive systems that treat any automated crawler as suspicious. The recommended policy is to allow the bot by User-Agent while applying a global threshold of 10 requests per minute from any single IP in its documented range to prevent accidental overload if multiple monitoring instances are activated simultaneously. Blocking is unnecessary because the bot respects robots.txt and carries explicit identification headers.

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the bots listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.