In today’s digital landscape, protecting and managing online assets is more essential than ever. Subdomains—integral extensions of primary domains—play a crucial role in structuring web services, improving user experience, and reinforcing brand identity. However, as digital infrastructures grow, monitoring and securing an expanding network of subdomains becomes a complex task. The Subdomains Explorer API meets this challenge with a robust solution designed for efficient subdomain discovery, evaluation, and management—strengthening cybersecurity and improving operational visibility.
To use this endpoint you must specify a domain in the parameter.
Subdomain Detection - Endpoint Features
| Object | Description |
|---|---|
domain |
[Required] Indicates a domain |
["1kqj8wt.feedproxy.ghs.google.com", "3thzdwuqpx7fydclvhbbpqti567faetn6onwgeco6y5aznnvlh5a.mx-verification.google.com", "abusereporting-pa.clients6.google.com", "accounts.google.com", "admob.google.com", "alt117.google.com", "ampcid.google.com", "analytics.google.com", "apis.google.com", "bigquery.clients6.google.com", "blackboard.google.com", "books.google.com", "chat-wsx.usercontent.google.com", "clients.l.google.com", "clients1.google.com", "clients2.google.com", "credit.microhost.google.com", "crowdsource-pa.clients6.google.com", "datamigration.clients6.google.com", "dialogflow.clients6.google.com", "drive.google.com", "drivesharefrontend-pa.clients6.google.com", "dynamicmail-pa.clients6.google.com", "encrypted.google.com", "europe-west12-cloudbuild.clients6.google.com", "firebaseappcheck-pa.clients6.google.com", "fitbit.google.com", "fundingchoicesmessages.google.com", "ghs.google.com", "ghs46.google.com", "googleadapis.l.google.com", "integrations.clients6.google.com", "jiients3.google.com", "khms.l.google.com", "lers.google.com", "lh7-qw.google.com", "mail-vk1-f181.google.com", "mapsphotoupload.clients6.google.com", "marketingplatform.google.com", "mobilesdk-pa.clients6.google.com", "mt1.google.com", "mt3.google.com", "mw-small.l.google.com", "nestservices.google.com", "notebooks.clients6.google.com", "notebooks.mtls.clients6.google.com", "ogads-pa.clients6.google.com", "ogs.google.com", "pages-beta.google.com", "patents.google.com", "pay.google.com", "payments.developers.google.com", "payments.google.com", "pixelrecorder-pa.clients6.google.com", "play_button.google.com", "playbooks-pa.clients6.google.com", "playconsoledevicedirectaccess-pa.clients6.google.com", "playconsolequalityfindings-pa.clients6.google.com", "policies.google.com", "pub-2166101631299917.afd.ghs.google.com", "r1---sn-aigl6n6s.c.docs.google.com", "r1.sn-aigl6n6s.c.docs.google.com", "r5---sn-qxaelnek.c.pack.google.com", "r5.sn-qxaelnek.c.pack.google.com", "rcs-acs-spectrum-us.jibe.google.com", "redirector.c.docs.google.com", "rr1---sn-5hne6n6e.c.docs.google.com", "rr1---sn-aigl6n6s.c.docs.google.com", "rr1---sn-aigl6n6s.c.drive.google.com", "rr1---sn-cvh7knle.c.drive.google.com", "rr1---sn-cvh7knzz.c.drive.google.com", "rr1---sn-h5576nss.c.docs.google.com", "rr1---sn-h5576nss.c.drive.google.com", "rr1---sn-qxaelnl7.c.docs.google.com", "rr1.sn-5hne6n6e.c.docs.google.com", "rr1.sn-5hne6n6e.c.drive.google.com", "rr1.sn-aigl6n6s.c.docs.google.com", "rr1.sn-aigl6n6s.c.drive.google.com", "rr1.sn-cvh76nez.c.docs.google.com", "rr1.sn-cvh7knle.c.drive.google.com", "rr1.sn-cvh7knzz.c.drive.google.com", "rr1.sn-h5576nss.c.docs.google.com", "rr1.sn-h5576nss.c.drive.google.com", "rr1.sn-qxaelnes.c.drive.google.com", "rr1.sn-qxaelnl7.c.docs.google.com", "rr2---sn-npoeener.c.drive.google.com", "rr2---sn-qxaeenld.c.docs.google.com", "rr2---sn-qxaeenld.c.drive.google.com", "rr2.sn-5hne6ns6.c.docs.google.com", "rr2.sn-npoeener.c.drive.google.com", "rr2.sn-qxaeenld.c.docs.google.com", "rr2.sn-qxaeenld.c.drive.google.com", "rr2.sn-qxaeenlz.c.docs.google.com", "rr2.sn-qxaeenlz.c.drive.google.com", "rr3---sn-5hne6n6e.c.chat.google.com", "rr3---sn-5hne6n6e.c.docs.google.com", "rr3---sn-5hne6n6e.c.drive.google.com", "rr3---sn-aigzrnz7.c.docs.google.com", "rr3---sn-qxaeeney.c.docs.google.com", "rr3.sn-5hne6n6e.c.chat.google.com", "rr3.sn-5hne6n6e.c.docs.google.com", "rr3.sn-5hne6n6e.c.drive.google.com", "rr3.sn-5hnekn76.c.drive.google.com", "rr3.sn-aigzrnz7.c.docs.google.com", "rr3.sn-qxaeeney.c.docs.google.com", "rr4---sn-cvh7kn6z.c.docs.google.com", "rr4---sn-cvh7kn6z.c.drive.google.com", "rr4---sn-h5576nsr.c.docs.google.com", "rr4---sn-h557sn66.c.mail.google.com", "rr4---sn-h557sn6z.c.drive.google.com", "rr4.sn-aigl6nsd.c.drive.google.com", "rr4.sn-cvh7kn6z.c.docs.google.com", "rr4.sn-cvh7kn6z.c.drive.google.com", "rr4.sn-h5576nsr.c.docs.google.com", "rr4.sn-h5576nss.c.docs.google.com", "rr4.sn-h557sn66.c.mail.google.com", "rr4.sn-h557sn6z.c.drive.google.com", "rr5---sn-aigl6nsr.c.chat.google.com", "rr5---sn-aigl6nsr.c.docs.google.com", "rr5---sn-aigl6nsr.c.drive.google.com", "rr5---sn-qxaelnek.c.docs.google.com", "rr5---sn-qxaelnek.c.drive.google.com", "rr5.sn-aigl6nsr.c.chat.google.com", "rr5.sn-aigl6nsr.c.docs.google.com", "rr5.sn-aigl6nsr.c.drive.google.com", "rr5.sn-aigzrn76.c.drive.google.com", "rr5.sn-qxaelnek.c.docs.google.com", "rr5.sn-qxaelnek.c.drive.google.com", "secureconnect-pa.clients6.google.com", "secureconnect-pa.mtls.clients6.google.com", "shell.cloud.google.com", "sites.google.com", "speak.google.com", "storage.clients6.google.com", "stream.meet.google.com", "suites.google.com", "support.google.com", "surveys.google.com", "tagassistant.google.com", "takeout-pa-qw.clients6.google.com", "trends.google.com", "trichoptera.sites.google.com", "upload.video.google.com", "us-east4.composer.cloud.google.com", "us-east4.datafusion.cloud.google.com", "usa-dialogflow.clients6.google.com", "wallet.google.com", "www.google.com", "www.r1---sn-aigl6n6s.c.docs.google.com", "www.r1.sn-aigl6n6s.c.docs.google.com", "x57wxojy33i3fvrgtzfl3m6knneyvcuid3p7mftyvz26rkcmbybq.mx-verification.google.com"]
curl --location --request GET 'https://zylalabs.com/api/6596/subdomains+explorer+api/9662/subdomain+detection?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 commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
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.
The Subdomains Detection endpoint returns a JSON array containing a list of subdomains associated with the specified domain. Each entry in the array represents a unique subdomain.
The response data is structured as a JSON array. Each element in the array is a string representing a subdomain, allowing for easy parsing and integration into applications.
The primary parameter for the Subdomains endpoint is the domain name. Users must specify this parameter to initiate the subdomain discovery process.
The Subdomains Detection endpoint provides information on all subdomains linked to a given domain, which can be used for security assessments, brand protection, and asset management.
Users can analyze the list of subdomains to identify potential security vulnerabilities, monitor for unauthorized subdomains, and maintain an updated inventory of web assets.
The data is sourced through advanced scanning techniques and domain enumeration methodologies, ensuring a comprehensive and accurate listing of subdomains.
Data accuracy is maintained through continuous updates and validation processes that ensure the subdomain information reflects the current state of the domain's online presence.
Typical use cases include conducting security audits, monitoring brand reputation, managing web assets, and performing penetration testing to identify vulnerabilities in subdomains.
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
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.
Service Level:
100%
Response Time:
7,016ms
Service Level:
100%
Response Time:
11,787ms
Service Level:
100%
Response Time:
18,196ms
Service Level:
100%
Response Time:
5,318ms
Service Level:
100%
Response Time:
1,157ms
Service Level:
100%
Response Time:
78ms
Service Level:
100%
Response Time:
1,813ms
Service Level:
100%
Response Time:
1,807ms
Service Level:
100%
Response Time:
1,999ms
Service Level:
100%
Response Time:
571ms
Service Level:
100%
Response Time:
133ms
Service Level:
100%
Response Time:
628ms
Service Level:
100%
Response Time:
1,026ms
Service Level:
100%
Response Time:
403ms
Service Level:
100%
Response Time:
802ms
Service Level:
100%
Response Time:
578ms
Service Level:
100%
Response Time:
731ms
Service Level:
100%
Response Time:
2,740ms
Service Level:
100%
Response Time:
918ms
Service Level:
100%
Response Time:
482ms