Trying to keep things off the internet will ALWAYS fail. Period.

It was designed to route around any problems, roadblocks, or controls put in place, because networks were sketchy as shit when the internet was invented. You had to expect that your poor data packet wouldn't be able to take a specific path between A and Z, because shit was always breaking.

So you had to make your little packet safe. And smart. And set up common "rules" around which all the intermediate devices would operate, to help your little packet on the way.

Everyone uses the Post as a metaphor for how data gets around the internet, and that is just wrong.

Here's how the internet works, whether you are sending an email, or connecting to a web site, or performing an ATM transaction:

1. You write your letter, and stick it in an envelope.

2. You write a 12-digit number on the outside of your letter. (Which may only be 8 digits. Or 9. Or 10. Or 11.)

3. You throw your letter out the open window.

4. It flutters down 10 stories to the street.

5. Someone picks it up, and reads the number on the front.

6. "Hm. Never heard of it. They hand it to the person next to them.

7. Repeat until someone recognizes the first 3 digits of the number.

8. "I know this one!"

9. They give the letter to a motorcycle messenger, and tell them where to take it.

10. The motorcycle messenger delivers the letter to the doorman.

11. The doorman looks at the number, and knows the first 6 digits. "Ok. I got it from here."

12. The motorcycle messenger tries to find you again, and tell you that they delivered the letter to the right building. They may or may not find you.

13. The doorman puts the letter in a chute to go down to the Mail Room.

14. The Mail Room knows the third set of numbers, and gets the letter to the right floor.

15. The floor warden knows the room from the last set of numbers, and delivers it to the door.

16. The secretary opens the letter and checks the language it was written in (SMTP, HTML, FTP, etc.)

17. She hands it to the person at the desk that handles that protocol.

18. That person looks at all of the different instances of that protocol running in their domain (HTTP, for example, and all the web sites they host from that room), and gives it to the correct server for processing.

19. The server reads the message. If it makes sense, it sends back one code. If it doesn't make any sense (or got wet/altered in transit) it sends a back a different code.

20. A messenger arrives at your door and says, "Message Received!"

21. You send the next part of your message. (Because that was just ONE PACKET, and a single email will take DOZENS of packets to send. Add an attachment, and that number goes to THOUSANDS of packets. For a single email message.)

Of course, in the intervening years since this process was invented, we have caches and smart scripts that make this process more efficient for the most popular sites in the world (wonder why that web site loads faster than the other one? Yeah. Your ISP has a local cache of it.), but this is how all information is exchanged on the internet.

And that envelope you threw out the window? There are TRILLIONS of them laying on the ground.

And the bike messenger that picks it up, reads it, and delivers it? There's a couple thousand of them.

---

tl;dr - You will never be able to police the placement of new content onto the internet. You cannot "stop" it. Or even shut it down. The entire system is designed to be resilient to any type of interference. Even governments that own the entire pipe and can shut down the internet in their country, cannot disable the cellular and satellite networks. So there is ALWAYS a path for the data to travel.