Stories
Slash Boxes
Comments

SoylentNews is people

Pirate Bay No Longer Uses Cloudflare, Visitors Sent to 'Black Hole'

posted by Fnord666 on Saturday April 11 2020, @02:35AM   Printer-friendly
from the you-can't-get-there-from-here dept.

upstart writes in with an IRC submission for chromas:

Pirate Bay No Longer Uses Cloudflare, Visitors Sent to 'Black Hole' * TorrentFreak:

The Pirate Bay's original and main domain has been unreachable for more than a month.

While the site operates as usual on the Tor network, visitors to ThePirateBay.org are welcomed by a Cloudflare error message mentioning that the "connection timed out."

Two weeks ago, a source familiar with the matter informed us that the infamous torrent site faces some technical issues and the admin is taking this opportunity to rewrite some code. After that, we received no updates.

Today, however, something appears to be changing. For the first time in years, the whois record for ThePirateBay.org has been updated. Instead of the domain pointing to Cloudflare's nameservers, it is now linked to the default nameservers of the domain registrar EasyDNS.

In addition, the domain's status code has changed from 'client Transfer Prohibited' to 'ok,' which means that there are no restrictions preventing it from being transferred to a new owner.

At the time of writing, all traffic to ThePirateBay.org is resolving to 127.0.0.1, which is the generic localhost IP-address. This means that the domain name is effectively null routed, with all requests dumped into a local black hole.

Original Submission

 
This discussion has been archived. No new comments can be posted.
Pirate Bay No Longer Uses Cloudflare, Visitors Sent to 'Black Hole' | Log In/Create an Account | Top | 22 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 3, Informative) by The Vocal Minority on Saturday April 11 2020, @04:12AM (4 children)

    by The Vocal Minority (2765) on Saturday April 11 2020, @04:12AM (#981018) Journal

    As does https://thepiratebay.org [thepiratebay.org]

    Starting Score:    1  point
    Moderation   +1  
       Informative=1, Total=1
    Extra 'Informative' Modifier   0  
    Karma-Bonus Modifier   +1  
    Total Score:   3  

  • (Score: 0) by Anonymous Coward on Saturday April 11 2020, @04:25AM

    by Anonymous Coward on Saturday April 11 2020, @04:25AM (#981020)

    ERR_CONNECTION_REFUSED

  • (Score: 2) by zocalo on Saturday April 11 2020, @08:23AM

    by zocalo (302) on Saturday April 11 2020, @08:23AM (#981066)
    That works for me here in the UK too, DNS also still resolving to a CloudFlare IP. I don't use the site often, but while the site has defintely been spotty of late I 'm pretty sure I've connected to it a few times at least and think I'd have probably noticed more than a month of continual downtime.

    Maybe it's an ISP or region specific thing, or the DNS/WHOIS record update is still propogating around the world? While I'm showing EasyDNS as the Whois registry, I'm still seeing Cloudflare as the DNS server provider, relevant records as at 8:20 UTC on April 11th:

    Domain Name: THEPIRATEBAY.ORG
    Registrar WHOIS Server: whois.easydns.com
    Updated Date: 2020-04-11T01:53:55Z
    Name Server: DEB.NS.CLOUDFLARE.COM
    Name Server: SEVKI.NS.CLOUDFLARE.COM

    ProTip: Whois != DNS.

    --
    UNIX? They're not even circumcised! Savages!

  • (Score: 2) by hendrikboom on Saturday April 11 2020, @07:52PM

    by hendrikboom (1125) Subscriber Badge on Saturday April 11 2020, @07:52PM (#981250) Homepage Journal

    When I try this I get a page:

    What happened?

    The initial connection between Cloudflare's network and the origin web server timed out. As a result, the web page can not be displayed.
    What can I do?
    If you're a visitor of this website:

    Please try again in a few minutes.
    If you're the owner of this website:

    Contact your hosting provider letting them know your web server is not completing requests. An Error 522 means that the request was able to connect to your web server, but that the request didn't finish. The most likely cause is that something on your server is hogging resources. Additional troubleshooting information here.
    ,/quote>

    Using dig, I get among other data,

    ;; ANSWER SECTION:
    thepiratebay.org. 300 IN A 104.18.36.27
    thepiratebay.org. 300 IN A 104.18.37.27

    That IP number isn't localhost.
    I have no problems pinging it.

    -- hendrik

  • (Score: 0) by Anonymous Coward on Sunday April 12 2020, @01:27PM

    by Anonymous Coward on Sunday April 12 2020, @01:27PM (#981497)

    https://thepiratebay.org/ [thepiratebay.org] works from Chicago area Sun Apr 12 13:21:24 UTC 2020

    https://thepiratebay.org/ [thepiratebay.org] works via tor

    http://piratebayztemzmv.onion/ [piratebayztemzmv.onion] also works