My previous blog post “Weaponizing favicon.ico for BugBounties , OSINT and what not” got quite a nice response(The tool “FavFeak made into TBHM recon edition by Jason Haddix too YAY).

and hence I decided to write blog posts more often and Hey see here is another blog post , grab a cup of coffee , sit tight and enjoy the blog post !

Long Story Short

In Bugbounties “If you are not first , then you are last” there is no such thing as silver or a bronze medal , Recon plays a very crucial part and if you can detect/Identify a newly added asset earlier than others then the chances of you Finding/Reporting a security flaw on that asset and getting rewarded for the same are higher than others.

Umm Makes sense ? Its all about leveling up your game

Lets dive into a bit technical stuff. Shall we?

SSL Certificates and CT logs

SSL Certificates bind together :

  • A domain name, server name or hostname.
  • An organizational identity (i.e. company name) and location.

Certificate Transparency logs are simple network services that maintain cryptographically assured, publicly auditable, append-only records of certificates. Anyone can submit certificates to a log, although certificate authorities will likely be the foremost submitters. Likewise, anyone can query a log for a cryptographic proof, which can be used to verify that the log is behaving properly or verify that a particular certificate has been logged.

More about CT logs can be found here :


Personally I am monitoring CT logs for domains/subdomains for quite a long time now and it gave me a lot of successful results , The inspiration behind this was Sublert : By yassineaboukir which checks for subdomains and can be executed periodically , However I am using somewhat different approach and instead of looking into periodically, I am extracting domains from Live CT log feeds , So chances of me finding a new asset earlier is higher as compared to others.

Building the required tooling

Desired workflow:

  • Monitoring Real Time CT log feed and extracting the domain names from that feed
  • Matching the extracted subdomains/domains against the domains/Keywords to be matched
  • Sending a Slack notification if a domain name matches

I am using Certstream for live CT log feed , CertStream is an intelligence feed that gives you real-time updates from the Certificate Transparency Log network, allowing you to use it as a building block to make tools that react to new certificates being issued in real time.


Along with this Blog post I am releasing this tool called “CertEagle” as well , Lets take a walkthrough on how to setup and use this.


  • A VPS (UNIX up and running)
  • Python 3x (Tested with Python 3.6.9)
  • Slack Workspace (optional)

I am assuming that you have already done with your setup of slack workspace .

Now Create a channel named “subdomain-monitor” and set up a incoming webhook

Enabling Slack Notifications:

Edit config.yaml file and paste your slack webhook URL there , It should look something like this:

Keywords and domains to match:

You can specify keywords and domains to match in domains.yaml file , You can specify names

For Matching subdomains :

Lets take as example , domains extracted from Real time CT logs will be matched against the word , if matched they will be logged in our output file (found-domains.log) . The thing to note here is , It will give some false positives like , but we can filter out them later on by using use regex magic

For Matching domains/subdomains with specific keywords

Lets assume that you want to monitor and log domains/subdomains that are having word “hackerone” in them, then our domains.yaml file will look something like this

Now all the extracted domains/subdomains that are having word hackerone in them will be matched and logged (and a slack notification will be sent to you for the same)

Okay we are done with our initial setup , Lets run our tool

$ python3

Matched domains will look like this :

Slack Notifications will look like this :

Note: You will not get notifications for duplicate domains/subdomains , CertEagle logs all the matched domains and if those domains will occur more than once in the real time CT logs then the notification about those domains will be sent only once.

Output files :

The program will keep on running all the matched domains will be saved under output directory in found-domains.log file

CertEagle can be found here : CertEagle Github

Want to support my work?

If you think my work has added some value to your existing knowledge, then you can Buy me a Coffee here (and who doesn’t loves a good cup of coffee?)



Subscribe to our Newsletter to get future articles/updates/blockchain-related news directly in your mailbox.