This site can’t be reached
irfanmanzil.wuaze.com’s server IP address could not be found.
Try:
Checking the connection
Checking the proxy, firewall and DNS configuration
Running Windows Network Diagnostics
ERR_NAME_NOT_RESOLVED
kindly resolve this issue, i recently checked my website.
Beep boop, I’m a bot! I dug through the forum to get you started. I sometimes get things wrong though, so do with this what you will until a human has a look.
Does https://irfanmanzil.wuaze.com show a green checkmark and an IP address on dnschecker.org for most locations? Please also tell me your internet provider and country, and what these two commands print when you run them in Command Prompt:
nslookup irfanmanzil.wuaze.com
nslookup irfanmanzil.wuaze.com 1.1.1.1
ERR_NAME_NOT_RESOLVED means your browser couldn’t look up which server the domain points to, so it never tried to connect. Our article on this error says the cause is either the domain setup or something between you and the internet, such as your provider’s DNS server. It says blocking by providers is most common with free subdomains. The results above show which of the two you have.
Here is the article. It also covers flushing your DNS cache and switching to a public DNS server if the problem turns out to be on your side:
I figured out the problem. Some carriers don’t resolve domains that have exhibited problems in the past. Wuaze is one. The carrier I’ve tested that will not resolve wuaze is T-Mobile. T-Mobile Taiwan resolves the domain correctly because T-Mobile is not a carrier in Taiwan, there are only 4 licensed cellular carriers in Taiwan, and T-Mobile is not one.
I have not tested all the domains on the infinityfree “free list” but I have tested all of the ones that don’t have “free” in their name. The domains on the free list for InfinityFree that do resolve using T-Mobile cellular system are
fwh.is
Infy.click
Page.gd
rf.gd
I spoke to a T-mobile admin, and they told me that there is some registrar issue with domains that have to be taken off-line for some reason. Probably bad actors. He was unable to tell me how to get the domains put back on-line with DNS support. I think this is an issue for Infinityfree, and the only workaround is what the bot suggested to me, which was move to a different domain.
Good luck
Jimbo
Yeh that happens
Unfortunately, a few bad actors ruin it for everyone 
How do you figure that exactly?
We’re not the operators of the DNS resolvers. We don’t control the blocklist. There might be tens of thousands of ISPs and DNS resolvers in the world, and we cannot monitor which provider blocks which domain name from our end.
When we know that a block is happening, we don’t always know how to find the operator of the DNS resolver, we cannot verify whether the domain is actually blocked (including verifying whether a block was removed), whether they have blocked it themselves or if they are using a third party blocklist (and if so, which one, and whether we can access it), or provide contact details to report a false positive.
You’re a paying customer. They have an obligation to provide you with a working internet service and they refuse to help you. What makes you think that they will welcome some company from the other side of the planet with no prior relation with them?
I understand your reply.
Back in my long ago history, I worked for a huge multinational company. Each division, and sometimes each huge facility would have it’s own subdomain. Our IT organization would send to a management list an email when the communication network went down and a list of facilities affected. So back in the 80’s there were tools that would check network integrity. Looking at How to Ping a Website or IP Address in 2026 — Commands and Online Test it seems those tools have evolved and are now commercially available. Sorry, I don’t know if this forum allows posting of a website, but that “ping” thing is on networktroubleshooting dot net. And I know ping has limitations, but they seem to have some higher level tools as well.
I’m guessing you host all the domains at IP location 31.22.x.x (just guessing) so a single point tool might be effective. Looking through the posts, it seems that there are quite a number that involve “my site’s gone dark” and “No certificate for this site” or other security-related feedback. (I saw one post “your site works fine on my machine” which leads me to believe this issue is significant enough to merit your investigation).
Per your reply above, I am pushing back on T-Mobile and both asked them to unblock Wuaze, on their cellular DNS servers (again assuming they are multi-homed and all will use the same block list). Also I have asked if they use a third party block list, and if so, who that is, maybe I can contact their customer support.
Anyway, once your domain owners know the issue exists for their site, they can call the appropriate customer support organization. But frankly I believe that an individual whining to a customer support organization for, say, T_Mobile, will get a lot less attention than getting contacted by a hosting company. Regardlesws of location.
Thanks for your reply. Best regards
Jimbo
Thank you very much! Please do keep us updated on the progress. If there is anything relevant they say about why they blocked the domain, or if they are willing to discuss the issue with us directly, I’d be happy to help.
That’s not really feasible.
I don’t think you understand how many DNS resolvers there are in the world. There are the big, public ones like Cloudflare, Google and Quad9. ISPs typically run their own, and ISPs come in many sizes, from big, national operators to small, local providers who only service a single city or even less. An office building a sometimes work at gets their internet from a managed hosting company that dabbles in networking on the side. And many organizations also run their own DNS resolvers, primarily so the organization’s IT and security departments can control how their network is used.
Monitoring all of them is impossible. Resolvers that aren’t public should be restricted so only their customers can use the resolvers, so monitoring them from the outside is impossible. So you’d have need to have a point inside the network where you could check the resolver status from. And when you’re dealing with, say, a school network, smuggling in a probe is just not feasible.
And that’s just DNS. Some providers do IP level blocks too. So you don’t just need to measure all free hosting domains, but also all free hosting IP addresses.
The complexity of deploying such a monitoring solution is insane, and I don’t think anyone in the world has something like this. Because by the time you’re big enough that deploying anything resembling it becomes feasible, you usually get enough traffic that you can just look at the loss of traffic from a certain ISP to conclude that there must be a block.
To be fair, quite a few of them are the “no certificate” complaint, but that’s not a blocking issue, that’s people who got a certificate for their own domain and aren’t giving it enough time for the installation to complete.
Still disagree with you there.
Starting a hosting company is actually not that difficult, so running a hosting company doesn’t automatically make you big and important. And ISPs know that. When Microsoft or Amazon comes knocking because their infrastructure is blocked, they will listen. But a small company like InfinityFree doesn’t have that kind of swing.
And then there are plenty of hosting companies who really don’t care what their customers do and look the other way while their customers are hosting spam, phishing and CSAM. So blocking an entire hosting provider is sometimes justified.
