Is the Facebook source dead, or am I doing it wrong? #1722
-
|
Hi, I'm having some issues getting the Facebook source to work, and while troubleshooting, I found that Meta no longer supports their Certificate Transparency Monitoring Tool (https://developers.facebook.com/docs/certificate-transparency/): According to Wayback Machine, the new page was scraped on 29th November, 2025 (https://web.archive.org/web/20250801000000*/https://developers.facebook.com/docs/certificate-transparency) I added this to my provider-config.yaml: And when I run "subfinder -d hackerone.com -s facebook -t 1 -rl 1 -v", I get this error: Can someone confirm whether I'm doing something wrong or if this source is dead? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
You are correct - the Facebook Certificate Transparency source is dead. Meta discontinued their CT monitoring tool in late 2025. The source should be removed from subfinder or marked as deprecated. Until then, you can exclude it: subfinder -d hackerone.com -all -es facebookThe Alternatively, dont include it in your provider-config.yaml at all. For CT-based subdomain enumeration, these sources still work well:
You might want to open an issue to have the Facebook source removed from the codebase since the upstream API no longer exists. |
Beta Was this translation helpful? Give feedback.
-
|
Issue has been created: #1727 |
Beta Was this translation helpful? Give feedback.

You are correct - the Facebook Certificate Transparency source is dead. Meta discontinued their CT monitoring tool in late 2025.
The source should be removed from subfinder or marked as deprecated. Until then, you can exclude it:
The
-esflag excludes specific sources.Alternatively, dont include it in your provider-config.yaml at all.
For CT-based subdomain enumeration, these sources still work well:
You might want to open an issue to have the Facebook source removed from the codebase since the upstream API no longer exists.