Header ads

Collapse

Announcement

Collapse
No announcement yet.

Looks like toiletstool.com is dead

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Looks like toiletstool.com is dead

    Or misconfigured -- it redirects to 127.0.0.1 and doesn't respond. It's been in operation since 2000 and was an initial refuge when Bianca's and the Daily Dump went down. Despite its maddening moderation policies, its inconsistent pretensions to being a family-friendly site, and its irregular posting schedule and navigation (going to a "previous page" meant going to a page that was later in time LOL), it was a repository for thousands of great wetting and pants-pooping stories. Some of them strained credulity, some of them described young children, some of them were in broken Japenglish, some of them were downright creepy. But some of them were classics. I hope I'm wrong, but if I'm not, rest in peace toiletstool.

  • #2
    Not so fast…

    Comment


    • #3
      I'm still getting the bad redirect. Maybe it's a country-specific thing or a DNS issue? Anyone else having this problem?
      Last edited by AccidentalTourist; September 30, 2025, 12:35 AM.

      Comment


      • #4
        works for me

        I am in the midwest USA, using a standard cable internet connection

        maybe try a VPN?

        the URL that works for me is https://www.toiletstool.com/

        In rare cases when something gets fouled up, I have found that the presence or absence of www. can make a difference in whether a site loads correctly

        Also, https:// is not the same as http://

        For most sites, either string will work. But in some cases only one will work.

        Try it four different ways. You may find that one of them works LOL

        https://www.toiletstool.com/
        http://www.toiletstool.com/
        https://toiletstool.com/
        http://toiletstool.com/

        Comment


        • #5
          Weird. I get internet over cable from comcast. My phone is on the verizon network. I've tried all 4 URLS on both computer and phone (phone with the wifi turned off so it's definitely Verizon) and I always get the 127.0.0.1 redirect. I guess I'll try VPN next, but I'm gonna need to educate myself a bit to set that up.

          Comment


          • #6
            Originally posted by AccidentalTourist View Post
            I always get the 127.0.0.1 redirect. I guess I'll try VPN next, but I'm gonna need to educate myself a bit to set that up.
            Have you cleared the cache in your browser? Tried a different browser?

            Proton VPN is good for beginners, from the same company that offers ProtonMail. There is a free version. Installation is easy. Uninstall is easy. No spam, no hidden bloatware or toolbars. Just be aware that the default setting may be to launch the program on startup. And simply launching the program is not the same as turning on the VPN. But if you are not using it regularly, you'll want to change that setting.

            Also, try visiting the toilet stool website from a computer at your local public library

            Or use the wi-fi in your doctor's office waiting room

            jk

            Comment


            • #7
              OK, after some experimentation, I've noticed that the website displays fine with some browsers but not others. Here is a summary of my findings:

              Microsoft Edge - Problem
              Google Chrome - Problem
              Firefox - No Problem
              Safari - No Problem
              Opera - Problem

              Comment


              • #8
                Hope that it gets fixed. Really like the site.

                But it still could be that the site is dying. Maybe time to save the content. I am not the best coder but maybe AI can solve it.

                Still remember the good old german forum with endless amount of nice content aurumh2o.de that was sadly never saved to my knowledge.

                Comment


                • #9
                  I was unable to reach the site on my mac with chrome, or on my pixel. But it works for me on Safari. Should have tried that first. I'm wondering whether it's a chrome issue or a google issue. Anyway, I'm back in business with Safari.

                  -- AT

                  Comment

                  Working...
                  X