Terms of Service
Last updated: 2026-11-10
1. Service Description
ContrastCyber ("we", "us") operates ContrastAPI at api.contrastcyber.com and the website at contrastcyber.com with its CVE pages (together, the "Service"). The Service is open to consumers and to businesses. ContrastAPI is a security data and monitoring API and MCP server. It answers questions about CVEs, public exploits, software packages, Windows drivers, domain names, TLS certificates, e-mail domains, IP addresses and image metadata. You can call it over REST, as the API quickstart shows. You can also call it as a Model Context Protocol (MCP) server, as the MCP setup guide shows. The Service is provided as is, with no warranty.
2. Informational Only
Every result of ContrastAPI is for information only. It is not a substitute for a professional security audit. CVE scores, exploit flags, IP address flags and domain checks come from public data sources and from our own rules. They may be incomplete, out of date, or wrong for your situation. Do not rely on our results alone for production security decisions, incident response or compliance attestation.
3. Acceptable Use
The Service reads public information. That includes vulnerability databases, DNS records, TLS certificates, domain registration data, Certificate Transparency logs, web archive capture lists, HTTP response headers and public block lists. We make no exploit attempt and no login or password attempt. We make no SMTP connection. The bot page lists every request the Service sends to another host. You agree not to:
- Use the Service for any illegal purpose.
- Try to overwhelm or disrupt the Service, for example with a DDoS attack or with automated requests beyond your hourly credits.
- Get around the rate limits, the authentication, or the limits the Service sets on its own requests to an upstream source.
- Resell raw API responses as a competing security data service without our written permission.
- Use results to help an attack, harassment, doxxing or unauthorized intrusion against a third party.
- Share, transfer or publish your Pro API key, or embed it in client-side code, a public repository or shared infrastructure.
- Use a lookup, such as the e-mail address check, to harvest personal data for marketing, profiling or stalking.
4. Free & Pro Plans
4.1 Free tier. The free tier needs no API key and no signup. It allows 30 credits per hour for each IPv4 address or IPv6 /64. You may use it for personal and commercial work. Every endpoint and MCP tool is open on the free tier, except the monitoring (watchlist) tools. Those need a Pro key.
4.2 Pro plan. A Pro key allows 500 credits per hour for each key. It also opens monitoring (watchlist) of CVEs, products, CVE searches, packages, domain names and IP addresses. You read its change events yourself, with watchlist_events. The pricing page shows the current price. Subscriptions are billed through our payment processors:
- Card payments go through Lemon Squeezy. They are billed monthly or yearly, as you choose, until you cancel.
- Crypto payments go through NOWPayments. Each one is a one-time invoice for a key that works for 30 days. Each payment gives a new key. It does not extend an older key. A monitoring list belongs to the key it was made with, so it does not move to the new key.
Refund policy. If you are not satisfied with a card subscription, ask for a refund within 14 days of your first payment. You then get it in full. A full refund ends your key at once. Renewals of a card subscription are not refunded. You can cancel at any time. Your key then keeps working until the end of the period you paid for.
A crypto payment for a Pro key is not refunded.
Nothing in these Terms limits a right that mandatory consumer law gives you.
By subscribing, you agree to keep your API key confidential. You are responsible for all usage under your key. You agree not to share or resell it. We may revoke an API key that violates these Terms, without refund. We may change prices and rate limits. We give existing subscribers 30 days notice before such a change.
4.3 Pay per call. A request without an API key may pay for one call with USDC on Solana, through the x402 protocol, on the REST endpoints and MCP tools that take payment. The price is the credit cost of the call at $0.01 per credit. The Service charges a payment only when the call is served: on a REST endpoint, when it answers 200, and on an MCP tool, when the tool result is served. Any other answer releases a payment that is not settled, and nothing is charged. A payment can be pending, which means the Service has not yet learned its result. Retry the call with the same payment, and do not sign a second one. A pending payment that the network has confirmed is paid, even when the call that found it was not served. A retry with the same payment then serves the call. One wallet can have one payment in flight at a time. The Service has no function that refunds a settled payment. If a payment was charged and the call was not served, write to us (see section 16), and we refund it by hand. This rule is for pay-per-call payments only. It does not change the rule above that crypto payments for a Pro key are not refunded.
5. Rate Limits
The free tier allows 30 credits per hour for each IPv4 address or IPv6 /64. A Pro key allows 500 credits per hour for each key. Each call costs credits, as the credit costs list shows. The budget resets at the start of each hour. The Service also caps its own requests to each upstream source, such as an RDAP server or Cert Spotter. All callers share each of those caps, so one caller can use up a cap for everyone. The bot page describes them.
6. Abusive Usage
We may block, throttle or ban any IP address, network, API key or user engaged in abusive usage. Abusive usage includes, but is not limited to, these acts: automated scraping beyond the rate limits, credential stuffing, cycling through many keys or addresses, bursts of requests aimed at a third party, and any activity that degrades the Service for other users. A block may cover one IP address, an address range or an API key.
7. Service Availability
The Service may change, be interrupted or be discontinued without notice. We do not guarantee uptime or availability, and we offer no service level agreement (SLA). We may add, change or remove endpoints and tools. Our data comes from public sources, and it can lag behind them. The /health endpoint reports the freshness of each data source. If we discontinue the Service, we refund the unused prepaid part of a card subscription. Crypto payments are not refunded, as section 4.2 says.
8. Data Collection
The Privacy Policy describes in full what the Service stores. In short:
- The rate limiter stores a keyed hash of your IP address, or a hash of your API key, with a credit count. That row stays at most 75 minutes from the start of its hour.
- An API key is stored as its SHA-256 hash. The database never holds the key itself.
- The usage log holds one line for each connection. A line holds no IP address, no API key, no query, no body and no argument value.
- Some answers are kept for a while and served to any caller who asks the same question. Such a kept answer holds no API key and no IP address of the caller.
- A Pro key's monitoring list holds the items you add to it.
You can call GET /privacy_my_data at any time. It returns the hash the Service metered your request by, and it links to the Privacy Policy.
9. Third-Party Lookups
Many endpoints look up data about third-party domain names, host names, IP addresses, e-mail addresses or organizations. You are responsible for making sure that your use of these lookups follows the laws that apply to you. Those may include data protection, anti-stalking, computer misuse and telecommunications laws. We do not check whether you are allowed to look up a given target. Some answers hold data from public catalogs and services. Their own terms and licences govern that data. The data sources and licenses section of the API documentation lists them.
A Pro key can save its own Shodan key or AbuseIPDB key, and ip_lookup then asks that vendor with it. The answer holds the vendor's data, from Shodan or from AbuseIPDB. The key owner is responsible for using a saved key under the terms of that vendor.
10. Intellectual Property
Catalog data belongs to its publishers. Examples are the CVE List, NIST NVD, CISA KEV, FIRST EPSS, MITRE CWE and MITRE D3FEND. Each publisher licenses its data under its own terms. The API documentation names the licence or the terms of each source.
11. Disclaimer of Warranties
THE SERVICE IS PROVIDED "AS IS" WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. WE DO NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, ERROR-FREE, OR FREE OF HARMFUL COMPONENTS. WE MAKE NO GUARANTEES ABOUT THE ACCURACY, COMPLETENESS, OR RELIABILITY OF ANY RESULTS, INCLUDING THIRD-PARTY THREAT DATA AND CVE METADATA.
12. Limitation of Liability
TO THE EXTENT THE LAW ALLOWS, IN NO EVENT SHALL CONTRASTCYBER BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES ARISING FROM YOUR USE OF THE SERVICE, INCLUDING BUT NOT LIMITED TO: DATA LOSS, SECURITY BREACHES RESULTING FROM RELIANCE ON API RESULTS, BUSINESS INTERRUPTION, MISSED VULNERABILITIES, OR LOSS OF PROFITS. TO THE EXTENT THE LAW ALLOWS, OUR TOTAL LIABILITY SHALL NOT EXCEED THE AMOUNT YOU PAID US IN THE 12 MONTHS PRECEDING THE CLAIM.
13. Indemnification
You agree to indemnify and hold harmless ContrastCyber from any claims, damages or expenses that arise from your use of the Service, from your violation of these Terms, or from your violation of a third party's rights. Such a violation includes an unauthorized lookup against a person or an organization.
14. Governing Law
The laws of the Republic of Turkey govern these Terms. The courts of Istanbul, Turkey, resolve any dispute. If you are a consumer, this choice does not take away the mandatory protections of the country where you live, or your right to go to its courts where that law gives it.
15. Changes to Terms
We may update these Terms at any time. When you keep using the Service, you accept the updated Terms. We announce material changes on this website.
16. Contact
For questions about these Terms, write to contact@contrastcyber.com.