Sublert is a security and reconnaissance tool which leverages certificate transparency to automatically monitor new subdomains deployed by specific organizations and issued TLS/SSL certificate.
MIT License
988
stars
166
forks
source link
Understanding the Process of `we couldn't find any subdomain` #47
I am struggling to understand why no [!] Added but unfortunately, we couldn't find any subdomain for anthropic.com as an example domain, could not be found.
If I navigate to https://crt.sh/ and perform a query for the Certificate Transparency DB, I do see matching entries:
Howdy
I picked a random example here: (
anthropic.com
)I am struggling to understand why no
[!] Added but unfortunately, we couldn't find any subdomain for anthropic.com
as an example domain, could not be found.If I navigate to https://crt.sh/ and perform a query for the Certificate Transparency DB, I do see matching entries:
10552791737 2023-10-01 2023-09-29 2023-12-28 anthropic.com anthropic.com C=US, O=Google Trust Services LLC, CN=GTS CA 1D4 10530892335 2023-09-29 2023-09-29 2023-12-28 anthropic.com anthropic.com C=US, O=Google Trust Services LLC, CN=GTS CA 1D4
I can confirm this is not a DNS-related error for example:
I ran a packet-capture on the host, I see the following DNS resolution process being performed:
This looks identical to a working example:
crt.sh here
Can somebody nudge me in the correct direction here? Is there a debug functionality I can run to understand why I yield zero results?
TYIA!