This page simply displays the HTTP referer as sent in the HTTP request headers (by the browser / user-agent), as well as your IP address and a bunch of other HTTP request headers.
referrer property has two
As returned from PHP's
Array ( [Host] => w3dk.com [User-Agent] => CCBot/2.0 (http://commoncrawl.org/faq/) [Accept] => text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 [X-Forwarded-For] => 184.108.40.206 [X-Cachewall-Remote-IP] => 220.127.116.11 [X-Cachewall-Object-Type] => dynamic [X-Cachewall-Server] => pluto.uksrv.co.uk [X-Cachewall-Proto] => http [X-Cachewall-Identity] => 40541246061455351 [Accept-Encoding] => gzip [Surrogate-Capability] => key=ESI/1.0 [X-Varnish] => 91455352 [Content-Length] => 0 )
For completeness, your reported IP address is:
$_SERVER['REMOTE_ADDR'] (PHP) = 18.104.22.168
Reverse lookup on IP address:
This is to test whether URL shortening services pass the referer.
In order to test the HTTP Referer when following a redirect, the following links all redirect back to this page in various ways:
replace()method) back to this page - Original Referer is lost and set to intermediary (redirect) page. Note that this method uses the
window.location.replace()method, so the intermediary/redirect page is replaced in the browser history.
hrefproperty) back to this page - Original Referer is lost and set to intermediary (redirect) page. This method assigns directly to the
window.location.hrefproperty, so the intermediary/redirect page is NOT replaced in the browser history.
See immediately what HTTP referer is passed when navigating from this non-SSL page. Note that navigating from HTTPS to HTTP the browser blocks the referer for security reasons. Navigating from HTTP to HTTPS there is no such security and the HTTP referer should be passed by the browser.
When clicking on a result in the Google SERPs (HTTPS) and navigating to here (an HTTP page), the HTTP Referer is still set to "https://www.google.co.uk" in most modern browsers (except IE). It is not blank as you might expect. This is probably due to the
<meta content="origin" name="referrer"> element in the
head section of the search results page.
In IE11, the HTTP Referer is set to: