The solution outlined below is believed to be obsolete & ineffective, but retained for historical interest. Phorm have changed their method of operation to hi-jack image requests. You should encrypt your web communications using SSL.

Dephormation Cookie Test

When a request is made to a non-standard http port, Phorms UID will probably 'leak' into the outside world. Phorm claim they ignore traffic other than http/port 80 so cannot prevent this leak occurring.

Download the Code Here

Zip archive is here to download.
Current md5sum a019aa20ccba211c8658e2e36d304681

Tar.gz archive is here to download.
Current md5sum 123d3021b7fd2f057a8d847433d2ca7f

The Status Image

This page includes a dynamic 'status' image.

  • Image turns red and displays an alert if a Phorm UID cookie is found.
  • Image turns yellow and displays a warning if a Phorm Partner ISP (BT/Virgin) is identified.
  • Image turns green and displays a message if neither a UID cookie or Phorm Partner ISP is found.

This image *must* be served from a non-standard http port (anything other than port 80) to be effective.

If the server is present on Phorms secret blacklist the image will only be partially effective because a Phorm UID cookie may not be available.

Joining the Phorm blacklist is a bonus for any web master who doesn't want to be part of Phorm's vile parasitic marketing scheme.

The image can be accessed using a url such as http://yourhost.com:yourport/yourpath/images.php

Current date is;
Wednesday 17th of August 2022 12:44:58 PM

Your hostname resolves to;
ec2-44-200-171-74.compute-1.amazonaws.com

Cookies revealed by connection to port 80;

Requesting image to test cookies;