> For the complete documentation index, see [llms.txt](https://sidxparab.gitbook.io/subdomain-enumeration-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sidxparab.gitbook.io/subdomain-enumeration-guide/active-enumeration/tls-csp-cname.md).
# TLS, CSP, CNAME Probing
## 1) TLS Probing
Nowadays generally all websites communicate over HTTPS(HyperText Transfer Protocol Secure). In order to use HTTPS, the website owner needs to issue an SSL(Secure Socket Layer) certificate.
This SSL/TLS(Transport Layer Security) certificate contains hostname belonging to the same organization.
Clicking on the "Lock🔒" button in the address bar, you can view the TLS/SSL certificate of any website.
For this purpose, we will be using a tool called [**Cero**](https://github.com/glebarez/cero)
#### Installation:
```bash
go install github.com/glebarez/cero@latest
```
#### Running:
```bash
cero in.search.yahoo.com | sed 's/^*.//' | grep -e "\." | sort -u
```
## 2) CSP Probing
In order to defend from the XSS attacks as well as keeping in mind to allow cross-domain resource sharing in websites CSP(Content Security Policies) are used. These CSP headers sometimes contain domains/subdomains from where the content is usually imported.
Hence, these subdomains can be helpful for us. In the below image we can see I extracted domains/subdomains from the CSP header of [twitter.com](https://twitter.com)
```
cat subdomains.txt | httpx -csp-probe -status-code -retries 2 -no-color | anew csp_probed.txt | cut -d ' ' -f1 | unfurl -u domains | anew -q csp_subdomains.txt
```
## 3) CNAME Probing
I personally came across 2-3 cases where visiting the CNAME of the website showed me the same website without a firewall. (I personally don't know why this happened)
Since then I probe the CNAME's of the subdomains found.
```
dnsx -retry 3 -cname -l subdomains.txt
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://sidxparab.gitbook.io/subdomain-enumeration-guide/active-enumeration/tls-csp-cname.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.