Wordpress(Tree at Directories level)
/wp-admin/
/css/
/images/
/includes/
/js/
/maint/
/network/
/user/
Wordpress(Tree at Directories level)
/wp-admin/
/css/
/images/
/includes/
/js/
/maint/
/network/
/user/
## IPv6 Tests | |
http://[::ffff:169.254.169.254] | |
http://[0:0:0:0:0:ffff:169.254.169.254] | |
## AWS | |
# Amazon Web Services (No Header Required) | |
# from http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html#instancedata-data-categories | |
http://169.254.169.254/latest/meta-data/iam/security-credentials/dummy | |
http://169.254.169.254/latest/user-data | |
http://169.254.169.254/latest/user-data/iam/security-credentials/[ROLE NAME] |
org: org_name | |
kibana content-length:217 | |
org:”Amazon” ssl:”target” | |
ssl:”target” | |
html:”Dashboard Jenkins” http.component:”jenkins” | |
http.title:”302 Found” | |
http.component%3A”java” | |
https://www.shodan.io/host/ip#9200 | |
https://www.shodan.io/host/ip | |
X-Redirect-By: WordPress ssl:”name” |
First, find directory names for the webroot. This would typically be www or public or something like that. How can we recognize these? By the files they contain. If a directory contains favicon.ico or index.html or robots.txt, it is pretty likely to be a webroot. Especially for robots.txt, because that only works if it is served on the root of the server. | |
.gitignore or README.md | |
Some Directories paths: | |
public | |
web | |
static | |
app | |
assets |