The URL Phishing Scanner API is a powerful tool that helps to protect individuals and organizations from the growing threat of phishing attacks. Phishing attacks are a type of cyberattack where an attacker tries to trick a user into revealing sensitive information, such as login credentials or financial details, by posing as a trusted source. These attacks can be devastating, leading to data breaches, financial losses, and reputational damage.
The URL Phishing Scanner API works by checking URLs against a database of known phishing attempts. When a user submits a URL to be checked, the API compares the URL against its database to see if it matches any known phishing attempts. If a match is found, the API can alert the user or organization that the URL is a potential phishing attempt.
One of the key benefits of the URL Phishing Scanner API is its speed and accuracy. With a fast and reliable API, users can quickly and easily check URLs to see if they are safe to visit. This can help individuals and organizations avoid potential phishing attacks, and can improve overall security.
Another benefit of the URL Phishing Scanner API is its ease of use. With a straightforward API, users can easily integrate phishing detection into their applications or security workflows. This makes it an ideal tool for security professionals, developers, and anyone else who needs to protect themselves or their users from phishing attacks.
Overall, the URL Phishing Scanner API is a critical tool for anyone looking to protect themselves or their organization from the growing threat of phishing attacks. By checking URLs against a database of known phishing attempts, this API can help users stay safe online and can prevent devastating data breaches and financial losses. Whether you're a developer, a security professional, or just someone who wants to stay safe online, the URL Phishing Scanner API is a must-have tool.
Email security: Email providers can use the URL Phishing Scanner API to scan links within emails for potential phishing attempts. This can help prevent users from accidentally clicking on malicious links and protect against phishing attacks.
Web browsers: Web browsers can integrate the URL Phishing Scanner API to warn users if they are about to visit a known phishing website. This can help users avoid being scammed and can enhance the overall security of the web browsing experience.
Cybersecurity software: Cybersecurity software can use the URL Phishing Scanner API to identify and block phishing attempts in real time. This can help protect users from being tricked into revealing sensitive information and can prevent data breaches.
Financial institutions: Financial institutions can use the URL Phishing Scanner API to protect their customers from phishing attacks. By scanning links in emails or on their website, financial institutions can provide an additional layer of security and build trust with their customers.
Social media platforms: Social media platforms can use the URL Phishing Scanner API to scan links shared on their platform for potential phishing attempts. This can help prevent malicious links from being spread on social media and can protect users from being scammed.
Besides API call limitations per month, there are no other limitations.
Check if a URL is a known phishing attempt
Get Status - Endpoint Features
Object | Description |
---|---|
url |
[Required] This is the URL that the API will check. Must be a valid HTTP(s) URL or it will throw a 400 |
{"status":200,"data":{"isScam":false,"domain":"paypa1-secure-login.com","detection":{"type":"domain"}}}
curl --location --request GET 'https://zylalabs.com/api/1934/url+phishing+scanner+api/1662/get+status?url=https://nytimes.com' --header 'Authorization: Bearer YOUR_API_KEY'
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The Get Status endpoint returns data indicating whether a submitted URL is a known phishing attempt. It provides a boolean value for "isScam," the domain checked, and details about the detection type.
The key fields in the response data include "status" (HTTP status code), "isScam" (boolean indicating if the URL is a phishing attempt), "domain" (the domain checked), and "detection" (providing details about the detection type).
The response data is structured in JSON format. It includes a top-level object with "status" and "data" fields, where "data" contains the phishing check results, including "isScam," "domain," and "detection."
The Get Status endpoint provides information on whether a URL is associated with phishing attempts, the specific domain checked, and the type of detection used, helping users assess the safety of URLs.
The Get Status endpoint primarily accepts a URL as a parameter for checking. Users should ensure the URL is properly formatted to receive accurate results.
Data accuracy is maintained through regular updates and quality checks against known phishing databases. This ensures that the API provides reliable and up-to-date information on potential threats.
Typical use cases include integrating the API into email security systems to scan links, enhancing web browsers to warn users of phishing sites, and supporting cybersecurity software in real-time threat detection.
Users can utilize the returned data by checking the "isScam" field to determine if a URL is safe. If "isScam" is true, they should avoid visiting the URL and consider implementing additional security measures.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the βX-Zyla-API-Calls-Monthly-Remainingβ field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
The βX-Zyla-RateLimit-Resetβ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, itβs important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
238ms
Service Level:
100%
Response Time:
224ms
Service Level:
100%
Response Time:
1,373ms
Service Level:
100%
Response Time:
1,394ms
Service Level:
100%
Response Time:
154ms
Service Level:
100%
Response Time:
515ms
Service Level:
100%
Response Time:
316ms
Service Level:
100%
Response Time:
302ms
Service Level:
100%
Response Time:
2,452ms
Service Level:
100%
Response Time:
11,993ms
Service Level:
100%
Response Time:
1,516ms
Service Level:
100%
Response Time:
4,515ms
Service Level:
100%
Response Time:
4,032ms
Service Level:
100%
Response Time:
1,029ms
Service Level:
100%
Response Time:
1,938ms
Service Level:
63%
Response Time:
2,982ms
Service Level:
100%
Response Time:
1,455ms
Service Level:
100%
Response Time:
2,683ms
Service Level:
100%
Response Time:
1,877ms
Service Level:
100%
Response Time:
5,115ms