Aug 15, 2017 04:47 PM
(This post was last modified: Aug 15, 2017 05:22 PM by StackFramed.)
Server Logging
The most commonly used method. Set up a logger on the site and get the server to embed it. Sometimes when you post an image on a site (a forum for example) the server will visit the image URL to preview it or host it on the forum on it's own. We can use this to our advantage by getting the server to visit the logger.
A good example for this would be image IP logging. You can create an image IP logger and embed the image onto the site. If it wants to host the image on it's own server, it'll have to visit the link to do so. Upon going to your link to retrieve the image, the server's backend should be logged. (Keep in mind that this doesn't always require you to use an image IP logger. As long as you can get the site to embed the link it should still give you it's IP)
Image IP loggers (Without the dashes):
https://iplo-gger.org/
http://www.fug-lekos.com/ip-grabber/index.html
https://gra-bify.link/
Email Resolving
You can use an email hosted with the site to find the backend server's IP by looking at it's headers. You'll just have to trigger the site to send an automated email to you.
A few of the most common ways you can do this is registering an account to your email, requesting password resets, or contacting administrators.
Header tracking tools:
http://whatismyipaddress.com/trace-email
Hosting History
If the site has been hosted on it's actual IP for a while prior to using a firewall, it's possible that crawlers have accessed it before and cached the information. Look up the site's hosting history and you might be able to find something.
Site report lookups:
http://toolbar.netcraft.com/site_report
http://viewdns.info/iphistory/
http://www.domainhistory.net/
Subdomain Resolving
The site could have subdomains whose records are under the real server's IP and not protected by the firewall. Try resolving the subdomains instead.
E.g. connecting to example.com will have an IP address belonging to Cloudflare, but mail.example.com is not protected by Cloudflare. Use that to your advantage.
Mass Scanning The Site's Host
The most advanced and challenging method to mitigate of them all. If you somehow know what host the site is using you can scan the entire host for matching content from a range of IP addresses.
E.g. if the site's host is Digital Ocean, what we can do is find the full range of IP addresses connected to Digital Ocean (http://bgp.he.net/search?search%5Bsearch...mit=Search). We can then take these IP addresses and compare them to the content on the site such as the page title or body using tools such as Nmap or Zmap.
IP Range Lookup:
http://bgp.he.net/
Useful Tools
http://skypegrab.net/cf.php
http://www.crimeflare.com/cfs.html
http://iphostinfo.com/cloudflare/
https://webresolver.nl/tools/cloudflare
http://www.skypeipresolver.net/cloudflare.php
https://www.cuteseotools.net/cloudflare-resolver
If you have anymore suggestions/methods feel free to post them below.
The most commonly used method. Set up a logger on the site and get the server to embed it. Sometimes when you post an image on a site (a forum for example) the server will visit the image URL to preview it or host it on the forum on it's own. We can use this to our advantage by getting the server to visit the logger.
A good example for this would be image IP logging. You can create an image IP logger and embed the image onto the site. If it wants to host the image on it's own server, it'll have to visit the link to do so. Upon going to your link to retrieve the image, the server's backend should be logged. (Keep in mind that this doesn't always require you to use an image IP logger. As long as you can get the site to embed the link it should still give you it's IP)
Image IP loggers (Without the dashes):
https://iplo-gger.org/
http://www.fug-lekos.com/ip-grabber/index.html
https://gra-bify.link/
Email Resolving
You can use an email hosted with the site to find the backend server's IP by looking at it's headers. You'll just have to trigger the site to send an automated email to you.
A few of the most common ways you can do this is registering an account to your email, requesting password resets, or contacting administrators.
Header tracking tools:
http://whatismyipaddress.com/trace-email
Hosting History
If the site has been hosted on it's actual IP for a while prior to using a firewall, it's possible that crawlers have accessed it before and cached the information. Look up the site's hosting history and you might be able to find something.
Site report lookups:
http://toolbar.netcraft.com/site_report
http://viewdns.info/iphistory/
http://www.domainhistory.net/
Subdomain Resolving
The site could have subdomains whose records are under the real server's IP and not protected by the firewall. Try resolving the subdomains instead.
E.g. connecting to example.com will have an IP address belonging to Cloudflare, but mail.example.com is not protected by Cloudflare. Use that to your advantage.
Mass Scanning The Site's Host
The most advanced and challenging method to mitigate of them all. If you somehow know what host the site is using you can scan the entire host for matching content from a range of IP addresses.
E.g. if the site's host is Digital Ocean, what we can do is find the full range of IP addresses connected to Digital Ocean (http://bgp.he.net/search?search%5Bsearch...mit=Search). We can then take these IP addresses and compare them to the content on the site such as the page title or body using tools such as Nmap or Zmap.
IP Range Lookup:
http://bgp.he.net/
Useful Tools
http://skypegrab.net/cf.php
http://www.crimeflare.com/cfs.html
http://iphostinfo.com/cloudflare/
https://webresolver.nl/tools/cloudflare
http://www.skypeipresolver.net/cloudflare.php
https://www.cuteseotools.net/cloudflare-resolver
If you have anymore suggestions/methods feel free to post them below.
Discord: StackFramed#1265
XMPP: [email protected]
Email: [email protected]
Skype: live:stackframed (Disabled)
