Is IDGod domain working?
No comments yet. Be the first to comment!
Please login to comment on this thread.
Thread Info
Thread Author
RE
regattaplates
Member since Aug 2025
16
Posts
4
Threads
43
Karma
Secure Payment Methods
Learn about the safest payment methods for online transactions. Bitcoin, gift cards, and more.
Learn More
VVL Vendors
Related Discussions
2025 Verified Vendor List (VVL)
0 replies
Fake ID Scam Websites - Updated 05/25/2025
0 replies
IDMaster Pro Review - Georgia ID Experience
29 replies
Elite ID Crafters Quality Analysis - Technical Deep Dive
0 replies
North American IDs Quality Analysis - Technical Deep Dive
0 replies
FastTrack IDs Customer Service Experience - Complete Breakdown
0 replies
Forum Moderators
🛡️
AdminFIDV
Administrator
⭐
Sterlingwalkeri
Moderator
⭐
Butter
Moderator
⭐
supermod
Moderator
Community Stats
Total Members:
719
Online Now:
0
Total Threads:
1,763
Total Posts:
6,661
Community Guidelines
New to our community? Read our guidelines for safe and respectful interactions.
Learn More
Checked IDGod's domain situation this morning because two people in my Discord mentioned getting certificate errors over the past few days. Here's what I actually found when I tested it myself.
What loaded and what didn't
The primary .com domain redirects to a different URL now — it's been doing this for a while, but the redirect destination has changed since the last time I checked. The current landing page loaded without errors in both Chrome and Firefox. The SSL certificate is valid with about eight months remaining. There's no interstitial warning or browser security flag when you visit directly.
The older mirror URL that some people still have bookmarked returns a 403 now. If you're getting certificate errors or blank pages, that's likely why — you're hitting an old URL that's no longer active. The new landing page is linked from their verified Dread post, which was updated about two weeks ago.
Login and account area
I could log into my account without issues. The order history page loaded correctly. The payment page rendered but I didn't complete a transaction, so I can't confirm payment processing end-to-end. I did see that the wallet address displayed on checkout matches the one they've been using since March, which is a good sign that the site hasn't been compromised or replaced with a phishing clone.
The certificate errors some people reported might be from cached DNS pointing to the old address, or from ISPs that haven't updated their routing. Clearing your browser cache and DNS cache, then navigating to the verified current URL fresh, resolved the issue for one person I walked through it with. If you're still seeing errors after that, post the specific error message — a certificate mismatch and a plain 403 are different problems with different causes.
One final note: bookmark the verified current URL from their signed Dread post rather than relying on search results. Search indexes cache old URLs for months after they stop working, and that's the most common reason people hit dead domains on an otherwise active vendor site.