In today's digital landscape, where websites and web applications are critical to users, managing and securing online assets is paramount. Subdomains play a crucial role in web infrastructure, serving as distinct branches of a main domain. However, monitoring and securing these subdomains can be a daunting task, especially when dealing with a large web presence. This is where the subdomain scanning API emerges as a vital tool, streamlining the process of discovering, evaluating and managing subdomains, ultimately bolstering web security and efficiency.
Subdomains are an integral part of a website's structure. They enable organizations to categorize and organize web content, create unique user experiences and enhance branding.
The Subdomain Tracker API provides comprehensive subdomain detection capabilities. By submitting a domain name, users can initiate a scan that systematically scans and identifies all associated subdomains. This process is thorough and efficient, ensuring that no subdomain goes undetected. The API leverages advanced scanning techniques and domain enumeration methodologies, making it a reliable asset for web administrators, security professionals and enterprises looking to maintain a complete inventory of their web assets.
Web security is a top priority for organizations, and subdomains are potential vectors for cyberattacks. The Subdomain Tracker API provides users with the tools they need to proactively assess the security of their subdomains. By identifying subdomains, users can perform vulnerability assessments, implement security measures and fortify these entry points against threats. This proactive approach to cybersecurity helps organizations stay one step ahead of malicious actors.
The Subdomain Tracker API is designed with flexibility in mind. It can be seamlessly integrated into existing web security and management workflows. Users can incorporate its functionality into their applications and scripts, enabling customized and automated subdomain discovery processes. This adaptability ensures that the API meets the specific needs of different organizations and use cases.
The Subdomain Tracker API is a valuable asset for organizations looking to improve web security and streamline web asset management. Its comprehensive subdomain discovery, cybersecurity enhancement capabilities and efficiency benefits make it an indispensable tool for users, web administrators, security professionals and enterprises of all sizes. Use the Subdomain Tracker API to strengthen your web infrastructure, protect your brand and ensure the integrity of your online presence in an ever-evolving digital environment.
It will receive parameters and provide you with a JSON.
Security audits: Organizations use the API to perform security audits by identifying and assessing subdomains for vulnerabilities and potential security risks.
Brand protection: Companies monitor subdomains to protect their brand reputation by detecting unauthorized or malicious subdomains that could damage their image.
Asset inventory: IT departments and web administrators maintain an up-to-date inventory of subdomains to ensure efficient web asset management.
Penetration testing: Ethical hackers and security professionals use the API to identify subdomains for penetration testing and vulnerability assessments.
Compliance audits: Enterprises leverage the API to assist in compliance audits, ensuring that all subdomains meet regulatory requirements.
Basic Plan: 200 API Calls. 3 requests per second.
Pro Plan: 400 API Calls. 3 requests per second.
Pro Plus Plan: 800 API Calls. 3 requests per second.
To use this endpoint you must specify a domain in the parameter.
Get Subdomains - Endpoint Features
Object | Description |
---|---|
domain |
[Required] |
["25www.google.com", "accounts.google.com", "ads.google.com", "adwords.google.com", "alt1.aspmx.l.google.com", "alt1.gmail-smtp-in.l.google.com", "alt1.gmr-smtp-in.l.google.com", "alt3.aspmx.l.google.com", "alt3.gmr-smtp-in.l.google.com", "alt4.gmail-smtp-in.l.google.com", "alt4.gmr-smtp-in.l.google.com", "android-market.l.google.com", "apis.google.com", "aspmx.l.google.com", "browserchannel-sites.l.google.com", "calljoy.area120.google.com", "captive.adservice.google.com", "clients.l.google.com", "code.l.google.com", "colab-alv.research.google.com", "colab-sandbox.research.google.com", "console.eu.cloud.google.com", "crowdsource.google.com", "dataplex-dev.cloud.google.com", "encrypted.google.com", "feelinsonice.appspot.l.google.com", "firebase.google.com", "get.duo.google.com", "ghs.google.com", "ghs.l.google.com", "gmr-smtp-in.l.google.com", "google-proxy-64-233-172-0.google.com", "google-proxy-64-233-173-0.google.com", "google-proxy-64-233-173-100.google.com", "google-proxy-66-102-7-0.google.com", "google-proxy-66-102-8-0.google.com", "google-proxy-66-102-8-100.google.com", "google-proxy-66-249-80-0.google.com", "google-proxy-66-249-82-0.google.com", "google-proxy-66-249-82-100.google.com", "google-proxy-66-249-83-0.google.com", "google-proxy-66-249-83-100.google.com", "google-proxy-66-249-84-0.google.com", "google-proxy-66-249-84-100.google.com", "google-proxy-66-249-88-100.google.com", "google-proxy-66-249-93-0.google.com", "google-proxy-66-249-93-100.google.com", "google-proxy-74-125-209-0.google.com", "google-proxy-74-125-210-100.google.com", "google-proxy-74-125-211-0.google.com", "google-proxy-74-125-211-100.google.com", "google-proxy-74-125-212-0.google.com", "google-proxy-74-125-213-0.google.com", "google-proxy-74-125-213-100.google.com", "google-proxy-74-125-215-100.google.com", "googlemail.l.google.com", "gsuite.google.com", "mail.google.com", "mobile.l.google.com", "myaccount.google.com", "ns1.google.com", "ns2.google.com", "ns3.google.com", "ns4.google.com", "ogs.google.com", "partnertest.fi.google.com", "play.google.com", "plus.l.google.com", "policies.google.com", "pub-4956638185816903.afd.ghs.google.com", "rate-limited-proxy-108-177-64-100.google.com", "rate-limited-proxy-108-177-65-100.google.com", "rate-limited-proxy-108-177-66-0.google.com", "rate-limited-proxy-108-177-66-100.google.com", "rate-limited-proxy-108-177-67-0.google.com", "rate-limited-proxy-108-177-69-0.google.com", "rate-limited-proxy-108-177-70-0.google.com", "rate-limited-proxy-108-177-70-100.google.com", "rate-limited-proxy-108-177-71-0.google.com", "rate-limited-proxy-108-177-72-0.google.com", "rate-limited-proxy-108-177-73-0.google.com", "rate-limited-proxy-108-177-73-100.google.com", "rate-limited-proxy-108-177-74-0.google.com", "rate-limited-proxy-108-177-74-100.google.com", "rate-limited-proxy-108-177-76-100.google.com", "rate-limited-proxy-108-177-77-0.google.com", "rate-limited-proxy-108-177-77-100.google.com", "rate-limited-proxy-108-177-79-0.google.com", "rate-limited-proxy-209-85-238-0.google.com", "rate-limited-proxy-209-85-238-100.google.com", "rate-limited-proxy-66-249-87-0.google.com", "rate-limited-proxy-66-249-89-0.google.com", "rate-limited-proxy-66-249-91-100.google.com", "rate-limited-proxy-72-14-199-0.google.com", "rate-limited-proxy-74-125-150-0.google.com", "rate-limited-proxy-74-125-150-100.google.com", "rate-limited-proxy-74-125-151-100.google.com", "rate-limited-proxy-74-125-218-100.google.com", "recorder.google.com", "sandbox.l.google.com", "smtp.google.com", "spf.google.com", "sslvideo-upload.l.google.com", "support.google.com", "talkgadget.l.google.com", "tensorboard-autopush.cloud.google.com", "tensorboard-staging.cloud.google.com", "time.google.com", "time3.google.com", "uberproxy-with-cn.l.google.com", "wifi.l.google.com", "www.google.com", "www3.l.google.com", "www4.l.google.com", "ytimg.l.google.com"]
curl --location --request GET 'https://zylalabs.com/api/2642/subdomain+tracker+api/2664/get+subdomains?domain=google.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 commitments. One click upgrade/downgrade or cancellation. No questions asked.
To use this API the user must indicate the URL of a domain to obtain its subdomains.
There are different plans suits everyone including a free trial for small amount of requests, but itβs rate is limit to prevent abuse of the service.
Zyla provides a wide range of integration methods for almost all programming languages. You can use these codes to integrate with your project as you need.
It is an API that allows users to easily obtain the subdomains of a domain.
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, look at the βX-Zyla-API-Calls-Monthly-Remainingβ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.
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 3600, it means 3600 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 let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.
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 trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.
Service Level:
100%
Response Time:
1,013ms
Service Level:
100%
Response Time:
507ms
Service Level:
100%
Response Time:
2,027ms
Service Level:
88%
Response Time:
12,959ms
Service Level:
100%
Response Time:
314ms
Service Level:
100%
Response Time:
320ms
Service Level:
100%
Response Time:
16,389ms
Service Level:
100%
Response Time:
139ms
Service Level:
100%
Response Time:
423ms
Service Level:
100%
Response Time:
54ms
Service Level:
100%
Response Time:
364ms
Service Level:
100%
Response Time:
6,234ms
Service Level:
100%
Response Time:
1,055ms
Service Level:
100%
Response Time:
489ms
Service Level:
100%
Response Time:
2,763ms
Service Level:
100%
Response Time:
88ms
Service Level:
100%
Response Time:
4,898ms