Suip - Biz: Localbitcoins Vds Donation Feedback
Suip - Biz: Localbitcoins Vds Donation Feedback
Suip - Biz: Localbitcoins Vds Donation Feedback
IP Ranges Composing
Report
Browsable location lists
and their IP addresses
All IP of locality
(region, city)
All IP of countries
All IP of ISPs
All IP of continents
All IP of Autonomous
System (AS)
IP ranges of all Internet
Service Providers (ISPs)
and organizations
Find out my IP
Find out your User >> RESPONSE INFO <<
Agent URL: https://www.vaksinhebat.idsolution.co.id/
Checking whether my Code: 200
real IP leaking (it tries Headers:
to reveal proxy) Date: Sun, 04 Jul 2021 17:45:00 GMT
Traceroute to me Server: CentOS WebPanel: Protected by Mod Security
X-Powered-By: PHP/5.6.37
Do I have IPv6
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Information Gathering Pragma: no-cache
Set-Cookie: PHPSESSID=dp5do6avieuvifdcgllalgrp20; path=/
Find out the location Connection: close
and Internet service Transfer-Encoding: chunked
provider by IP Content-Type: text/html; charset=UTF-8
Find out the location If you want to contribute,
and Internet service >> RESPONSE HEADERS DETAILS << you can make donation for
provider by IPv6 Header Field Name: Transfer-Encoding
adding new services:
IP or Websites Value: chunked
Reference: https://tools.ietf.org/html/rfc7230#section-3.3.1
Information Gathering PayPal:
Security Desсription: Response splitting (a.k.a, CRLF injection) is a common technique,
Identify CMS of used in various attacks on Web usage, that exploits the line-based nature of HTTP message [email protected]
Websites framing and the ordered association of requests to responses on persistent connections. Bitcoin: Click for
WebApp Information This technique can be particularly damaging when the requests pass through a shared cache. Address
Gatherer Security Reference: https://tools.ietf.org/html/rfc7230#section-9
Generate and test Recommendations: A common defense against response splitting is to filter requests for data
domain typos and that looks like encoded CR and LF (e.g., "%0D" and "%0A"). However, that assumes the
variations application server is only performing URI decoding, rather than more obscure data
transformations like charset transcoding, XML entity translation, base64 decoding, sprintf
Web-sites on a single IP
reformatting, etc. A more effective mitigation is to prevent anything other than the
IP address of a web-site server's core protocol libraries from sending a CR or LF within the header section, which
IP address history of means restricting the output of header fields to APIs that filter for bad octets and not
web sites allowing application servers to write directly to the protocol stream.
List ALL DNS records CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site
Viewing specific DNS Scripting')
records of a site CWE URL: https://cwe.mitre.org/data/definitions/79.html
HTTP response headers
Trace URL's jumps Header Field Name: Set-Cookie
Value: PHPSESSID=dp5do6avieuvifdcgllalgrp20; path=/
across the rel links to
Reference: https://tools.ietf.org/html/rfc6265
obtain the last URL Security Desсription: Cookies have a number of security pitfalls. In particular, cookies
Checking the existence encourage developers to rely on ambient authority for authentication, often becoming
of a given mail vulnerable to attacks such as cross-site request forgery. Also, when storing session
Check the existence of identifiers in cookies, developers often create session fixation vulnerabilities.
a profile Transport-layer encryption, such as that employed in HTTPS, is insufficient to prevent a
Search for profiles by network attacker from obtaining or altering a victim's cookies because the cookie protocol
full names itself has various vulnerabilities. In addition, by default, cookies do not provide
confidentiality or integrity from network attackers, even when used in conjunction with
Checking the existence
HTTPS.
of domains Security Reference: https://tools.ietf.org/html/rfc6265#section-8
Convert IP address to Recommendations: Please at least read these references:
hostname https://tools.ietf.org/html/rfc6265#section-8 and
Autonomous System https://www.owasp.org/index.php/Session_Management_Cheat_Sheet#Cookies.
Number Lookup by IP CWE: CWE-614: Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
Address CWE URL: https://cwe.mitre.org/data/definitions/614.html
Search user in social
media Header Field Name: Server
Value: CentOS WebPanel: Protected by Mod Security
OSINT Tool for All-In-
Reference: https://tools.ietf.org/html/rfc7231#section-7.4.2
One Web Security Desсription: Overly long and detailed Server field values increase response
Reconnaissance latency and potentially reveal internal implementation details that might make it
(slightly) easier for attackers to find and exploit known security holes.
Information exfiltration Security Reference: https://tools.ietf.org/html/rfc7231#section-7.4.2
from cache and web Recommendations: An origin server SHOULD NOT generate a Server field containing needlessly
archives fine-grained detail and SHOULD limit the addition of subproducts by third parties.
CWE: CWE-200: Information Exposure
Display page from CWE URL: https://cwe.mitre.org/data/definitions/200.html
Google cache
Header Field Name: Pragma
Simultaneous search in
Value: no-cache
several web archives Reference: https://tools.ietf.org/html/rfc7234#section-5.4
Security Desсription: Caches expose additional potential vulnerabilities, since the
IP calculators contents of the cache represent an attractive target for malicious exploitation.
Security Reference: https://tools.ietf.org/html/rfc7234#section-8
IP Subnet Calculator Recommendations: The "Pragma" header field allows backwards compatibility with HTTP/1.0
IPv6 Subnet Calculator caches, so that clients can specify a "no-cache" request that they will understand (as
IP address converter Cache-Control was not defined until HTTP/1.1). When the Cache-Control header field is also
IP address aggregator present and understood in a request, Pragma is ignored. Define "Pragma: no-cache" whenever
Network Ranges in is possible.
CIDR CWE: CWE-524: Information Exposure Through Caching
CWE URL: https://cwe.mitre.org/data/definitions/524.html
Split subnet by
Network Mask Header Field Name: Cache-Control
Split subnet by size Value: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Binary IP to standard Reference: https://tools.ietf.org/html/rfc7234#section-5.2
view Security Desсription: Caches expose additional potential vulnerabilities, since the
Converting IP contents of the cache represent an attractive target for malicious exploitation. Because
Addresses to Binary cache contents persist after an HTTP request is complete, an attack on the cache can reveal
Decimal IP to normal information long after a user believes that the information has been removed from the
network. Therefore, cache contents need to be protected as sensitive information.
form
Security Reference: https://tools.ietf.org/html/rfc7234#section-8
IP to Decimal Recommendations: Do not store unnecessarily sensitive information in the cache.
Hexadecimal IP to CWE: CWE-524: Information Exposure Through Caching
normal form CWE URL: https://cwe.mitre.org/data/definitions/524.html
IP to Hexadecimal
Number Header Field Name: Content-Type
Octal number to IP Value: text/html; charset=UTF-8
IP to octal number Reference: https://tools.ietf.org/html/rfc7231#section-3.1.1.5
Security Desсription: In practice, resource owners do not always properly configure their
Bypassing the prohibition origin server to provide the correct Content-Type for a given representation, with the
result that some clients will examine a payload's content and override the specified type.
of displaying source Clients that do so risk drawing incorrect conclusions, which might expose additional
HTML code, bypassing security risks (e.g., "privilege escalation").
social content lockers Security Reference: https://tools.ietf.org/html/rfc7231#section-3.1.1.5
Recommendations: Properly configure their origin server to provide the correct Content-Type
Service bypassing for a given representation.
blocking view source CWE: CWE-430: Deployment of Wrong Handler
page CWE URL: https://cwe.mitre.org/data/definitions/430.html
Bypassing social
>> RESPONSE MISSING HEADERS <<
content lockers
Header Field Name: X-Frame-Options
Reference: https://tools.ietf.org/html/rfc7034
Advanced search engines Security Desсription: The use of "X-Frame-Options" allows a web page from host B to declare
usage that its content (for example, a button, links, text, etc.) must not be displayed in a
frame (frame or iframe) of another page (e.g., from host A). This is done by a policy
Advanced Google declared in the HTTP header and enforced by browser implementations.
search Security Reference: https://tools.ietf.org/html/rfc7034
Recommendations: In 2009 and 2010, many browser vendors ([Microsoft-X-Frame-Options] and
Encoding [Mozilla-X-Frame-Options]) introduced the use of a non-standard HTTP [RFC2616] header field
"X-Frame-Options" to protect against clickjacking. Please check here
Encoding detection and https://www.owasp.org/index.php/Clickjacking_Defense_Cheat_Sheet what's the best option for
encoding convertor your case.
CWE: CWE-693: Protection Mechanism Failure
Anti CloudFlare CWE URL: https://cwe.mitre.org/data/definitions/693.html
HTTPS: N
techniques
Header Field Name: Frame-Options
Whether a site behind Reference: https://tools.ietf.org/html/rfc7034
CloudFlare Security Desсription: The use of "X-Frame-Options" allows a web page from host B to declare
Utilize misconfigured that its content (for example, a button, links, text, etc.) must not be displayed in a
DNS and old database frame (frame or iframe) of another page (e.g., from host A). This is done by a policy
records to find hidden declared in the HTTP header and enforced by browser implementations.
IP's behind the Security Reference: https://tools.ietf.org/html/rfc7034
CloudFlare network Recommendations: In 2009 and 2010, many browser vendors ([Microsoft-X-Frame-Options] and
Disclosure of real IP of [Mozilla-X-Frame-Options]) introduced the use of a non-standard HTTP [RFC2616] header field
"X-Frame-Options" to protect against clickjacking. Please check here
sites are behind
https://www.owasp.org/index.php/Clickjacking_Defense_Cheat_Sheet what's the best option for
Cloudflare, Incapsula, your case.
SUCURI and other WAF CWE: CWE-693: Protection Mechanism Failure
CWE URL: https://cwe.mitre.org/data/definitions/693.html
Images and Metadata HTTPS: N
Converting geographic
coordinates from
decimal to degrees,
minutes and seconds
format
Converting geographic
coordinates from
degrees to decimal
format
QR codes
Special pages