Skip to main content
[email protected] 24/7 Support
Menu

FakeYourDrank website domain check

posted by mauri43 2 months ago 486 views 0 comments

I checked the FakeYourDrank domain situation this morning because there's been confusion in recent threads about which URL to use. Here's what I found from my testing.

The main domain is currently resolving correctly and the site loads without redirect issues when accessed directly. I tested it from two different connections — one with a VPN active and one without — and both loaded the homepage cleanly. Login and the order form area were functional in my tests. The SSL certificate was valid and issued to the expected domain name rather than a generic hosting certificate, which is what you want to see.

There's a secondary domain that was circulated in some forum threads last month that is no longer resolving. If you bookmarked a FakeYourDrank link from a thread that's more than about six weeks old, it's possible you're hitting that dead secondary domain. Try navigating directly to the main domain from a fresh browser tab rather than following an old link.

One sign that you're on the correct FakeYourDrank site: the order form asks for your state selection first and then presents the personalization fields. If you're landing on a page that immediately asks for payment information or personal details before giving you a state selector and design preview, you're not on the genuine site and should close the tab and re-navigate.

I've also noticed that FakeYourDrank has been blocking some datacenter IP ranges, which can cause their site to appear down if you're using a VPN with a datacenter endpoint. If the main domain isn't loading through your VPN, try a residential VPN endpoint or try accessing directly without VPN. A site that loads without VPN but not with VPN is blocking your VPN's IP range, not actually down.

Current status as of my test this morning: operational, main domain working, secondary domain from older links is dead. If you're having trouble loading it, the most likely issue is an old bookmarked URL or VPN IP range blocking.

4

No comments yet. Be the first to comment!

Please login to comment on this thread.