Per a request from Javaun, this bug is created to track the work for creating a shell website to simulate malicious trackers. This will be used as part of the Tracking Protection UITour. Some rough steps - register domain - establish hosting - creative and copy - blacklist the domain in product

marking as employee confidential until we own the domain name, so we can talk about stuff here.

As part of the manual test on bug 1149825, we now also own: - itisatracker.org - itisatracker.com because we need two blocked domains for that test. Should we kill one of these domains (trackertest.org, itisatracker.org, itisatracker.com)?

Our Engagement Engineering team needs one blocked domain and needs the hosting behind it to be very resilient for use in the UI tour. We need two domains for manual testing in bug 1149825, one of them could be the same domain used in the UI tour. In the near future (43?) we will likely need another domain, that contains fake tracker loads, that is *not* hardcoded as blocked in platform. This would be a unblocked domain full of loads that developers could use to test blocker add-ons they write on top of the platform TP APIs. Francois, want to drop one of yours? I think they're already rolling on trackertest.org and are setting up SSL because we need that for UI tour.

We shouldn't literally kill one of these 3, btw, just not hardcode it as blocked in platform. We'll need an unblocked one soon enough.

Ok, let's block: - trackertest.org - itisatracker.org and we'll save itisatracker.com for later.

Francois: I think everything here is complete. Can you verify and if so close this out?

I have verified that all three sites work both on HTTP and HTTPS. Thanks everyone!