Subdomain Finder

Discover subdomains via certificate transparency, then show CDN, ASN, and datacenter per row.

Subdomains of sharktech.net

43 found in CT logs Source: CertSpotter Probed: 30 Unique ASNs: 2
Subdomain IP ASN / Network CDN Datacenter
admin.smp.sharktech.net 64.32.25.26 AS46844 SHARKTECH - Sharktech - -
ams.sharktech.net 45.58.151.11 AS46844 SHARKTECH - Sharktech - -
amsspeed.sharktech.net 45.58.159.116 AS46844 SHARKTECH - Sharktech - -
api.smp.sharktech.net 64.32.25.26 AS46844 SHARKTECH - Sharktech - -
apifw-dev.sharktech.net 67.21.64.106 AS46844 SHARKTECH - Sharktech - -
backup.sharktech.net 162.244.7.69 AS53991 ACRONIS-53991 - Acronis - -
benchmark.sharktech.net 45.58.165.35 AS46844 SHARKTECH - Sharktech - -
chi.sharktech.net 204.188.230.181 AS46844 SHARKTECH - Sharktech - -
chispeed.sharktech.net 204.188.228.225 AS46844 SHARKTECH - Sharktech - -
den.sharktech.net 70.39.67.217 AS46844 SHARKTECH - Sharktech - -
denspeed.sharktech.net 70.39.90.55 AS46844 SHARKTECH - Sharktech - -
image.scp-ams.sharktech.net 45.58.159.48 AS46844 SHARKTECH - Sharktech - -
image.scp-chi.sharktech.net 204.188.228.208 AS46844 SHARKTECH - Sharktech - -
image.scp-den.sharktech.net 70.39.90.179 AS46844 SHARKTECH - Sharktech - -
image.scp-las.sharktech.net 208.98.35.40 AS46844 SHARKTECH - Sharktech - -
image.scp-lax.sharktech.net 45.58.179.95 AS46844 SHARKTECH - Sharktech - -
jf-dev.sharktech.net 45.58.165.246 AS46844 SHARKTECH - Sharktech - -
kuma.sharktech.net 64.32.16.112 AS46844 SHARKTECH - Sharktech - -
las.sharktech.net 208.98.33.23 AS46844 SHARKTECH - Sharktech - -
lasspeed.sharktech.net 208.98.36.221 AS46844 SHARKTECH - Sharktech - -
lax.sharktech.net 45.58.177.187 AS46844 SHARKTECH - Sharktech - -
laxspeed.sharktech.net 45.58.179.29 AS46844 SHARKTECH - Sharktech - -
leantime.sharktech.net 45.58.179.58 AS46844 SHARKTECH - Sharktech - -
monitor.vpscp.sharktech.net 64.32.27.144 AS46844 SHARKTECH - Sharktech - -
nms.sharktech.net 70.39.65.209 AS46844 SHARKTECH - Sharktech - -
ookla.la.ca.sharktech.net 64.32.16.6 AS46844 SHARKTECH - Sharktech - -
prox-ams.sharktech.net 45.58.145.194 AS46844 SHARKTECH - Sharktech - -
prox-chi.sharktech.net 204.188.199.66 AS46844 SHARKTECH - Sharktech - -
prox-den.sharktech.net 70.39.111.194 AS46844 SHARKTECH - Sharktech - -
prox-las.sharktech.net 208.98.46.2 AS46844 SHARKTECH - Sharktech - -
13 more subdomains found but not probed (cap is 30 per run)
prox-lax.sharktech.net s3metrics.sharktech.net sharktech.net smp.sharktech.net speedtest.chi.sharktech.net speedtest.den.sharktech.net titan.sharktech.net vap.sharktech.net whmcs.scp-ams.sharktech.net whmcs.scp-chi.sharktech.net whmcs.scp-den.sharktech.net whmcs.scp-las.sharktech.net whmcs.scp-lax.sharktech.net

About Subdomain Finder

This tool finds subdomains by querying certificate transparency logs at crt.sh, which records every TLS certificate issued by every public CA. Any subdomain that has ever held a cert appears in the result. For each discovered subdomain (capped at 30 active probes per run for speed), the tool resolves the current IP, looks up the ASN via RIPE stat, identifies the CDN vendor if any, and cross-references the network operator against our datacenter directory to surface the facility provider where possible.

When to use it

Run this during a security assessment to map a target's externally visible attack surface. Use it during competitor research to see which subdomains they expose for marketing landing pages, staging environments, or APIs. Sysadmins use it after a migration to confirm every active subdomain points at the new infrastructure and none still point at the old origin.

How to read the results

Total found is the count from CT logs, which can include historical subdomains that no longer resolve. The probed rows show current state: IP, ASN, holder, and detected CDN. The Datacenter column links to our internal datacenter directory when the AS holder matches an operator in our directory, which often reveals the physical facility where traffic terminates. Empty CDN cells mean the subdomain is served direct from origin or uses a non-standard CDN.

Frequently asked questions

Why are some subdomains in the CT logs but do not resolve?

CT logs record every certificate ever issued, including for subdomains the owner has since retired. The host might have stopped using the name, removed the DNS record, or shut down the service. The cert remains in the public log permanently.

Why is the result capped at 30 active probes?

Each probe involves DNS resolution and an ASN lookup at RIPE. Synchronous PHP requests time out beyond 30 to 60 seconds, so we cap the probe count to fit. The remaining subdomains are shown in a list so you can paste any specific one back into the tool for a fresh lookup.

Can I find subdomains that never had a TLS certificate?

Not through this tool. Pure HTTP subdomains, internal-only DNS, or subdomains using self-signed certs do not appear in public CT logs. Wordlist-based brute force tools can find some of those, but at the cost of being noisy and slow.

What does the Datacenter column tell me?

When the ASN holder matches an operator we have facilities for, the column links to that operator's datacenter pages. This tells you which physical infrastructure provider serves the subdomain. For CDNs the operator is the CDN itself, since the user-facing IP terminates at the edge node.

Who Is Online

In total there are 73 users online: 0 registered, 66 guests and 7 bots.

Bots: DuckDuckBot Facebook Googlebot Other Bot Other Crawler Other Spider SemrushBot

Users active in the past 15 minutes. Total registered members: 340