All You Need to Know About MOFH (MyOwnFreeHost)

Hi everyone! :waving_hand:

Over the past few weeks, I’ve been researching MOFH (MyOwnFreeHost) — the free reseller hosting system by iFastNet that powers many free hosting platforms, including InfinityFree itself.

To help new users, curious developers, or anyone interested in what MOFH’s history & key-features etc are, I’ve compiled my findings into a simple and structured GitHub site:

:link: Check it out here: MyOwnFreeHost & iFastNet Research

4 Likes

This is intresting. I’d been asked by my local makerspace to look into an option that would allow members to set up their own project sites. I was looking at MOFH but this has actually been really helpful :slight_smile:

2 Likes

Hey, that sounds awesome! Glad the post helped you out. MOFH can definitely be a solid option for makerspaces or communities looking to offer project hosting. If you do explore it further or end up building something for your space, I’d love to hear how it goes!

2 Likes

Small thing I noticed, you stated unlimited bandwidth space etc in the beginning, but then corrected yourself with the real limits below. I would update that top paragraph for accuracy :slight_smile:

5 Likes

… wanted to reply…but didn’t mention…

Thank you for pointing that out! I understand where the confusion might have come from.

Just to clarify—when I mentioned “unlimited” features, I was specifically referring to resellers, not individual end-users. In both the Reseller Benefits and Pricing Structure sections, the term “unlimited” was used in the context of what’s available to resellers through the MyOwnFreeHost platform—like unlimited disk space, bandwidth, domains, and databases for the reseller’s operation.

Later in the, report, I did mention the user-level limitation (e.g., max 3 accounts per user), which applies to general users—not resellers. Resellers themselves can create as many user accounts as they want, without that limitation.

5 Likes

For people with little to no knowledge of programming/coding, having your own hosting could be too much of homework. I’d stick to infinityfree.

1 Like

There are a few points on the article I don’t think are entirely accurate.

White-Labeling

You repeat multiple times how everything is white-label. But you never mention the iFastNet upgrade offers in the control panel, or the requirement to have iFastNet promotion on your website.

The only reason that MOFH is free is that it helps bring paying customers to iFastNet, so this is an important nuance to state I think.

MOFH provides for resellers to incorporate their own advertising code, such as Google Adsense

AdSense, and most reputable ad providers, require per-domain approval of ads, usually through the setup of an ads.txt file to authorize sellers to advertise on a given domain name. The testcookie system may interfere with this, and makes it basically impossible to put AdSense ads on customer websites.

Then there is also the fact that AdSense and other reputable ad networks are quite picky about what content they will advertise on. This makes it very dangerous to inject ad code into user websites, as it risks getting your entire AdSense account terminated when your ad code is being included in a phishing site for example.

High-speed SSD servers

Basically the default everywhere now. Even free hosting is all SSD/NVMe storage. HDDs are just too slow.

Integrated CloudFlare support

Not true. The cPanel integration from Cloudflare was abandoned, and Cloudflare Railgun that you see advertised also no longer exists.

100 GB monthly bandwidth

Not true as far as I know. It’s parroted a lot, but over the 9+ years and millions of websites I have been responsible for, I have never seen a single case of anyone ever hitting anything resembling a bandwidth limit.

Up to 50 domains hosted

Not true. You are limited to 50 subdomains, but there is no limit to the number of addon domains.

9 Likes

The inaccurate points in the article were gathered from a variety of sources. I compiled this information during my research, drawing mainly from several non-official websites that offered limited or partial insights on the topic.

Now, this is exactly the kind of input I was hoping to receive from an experienced individual like yourself. Thank you so much for sharing, @Admin—I truly appreciate it.
I will definitely make the necessary changes to the article soon. :slight_smile:
I have made the necessary changes—you can see them here.

3 Likes

literally theres a .php at the end of their webpages oh my god would expect more from a profrossional company that is so funny lmfao

I have seen you mention the same thing to somewhere else on the forum, first of all that (.php) or (.html) states in which programming language the page is rendered, and yeah THIS IS A COMMAN KNOWLEDGE…which i assume you do not possess, how are you even on this platform mate?

And yeah wth you mean by this? ?

1 Like

Slightly off topic, but I really don’t understand this sentiment behind “.php extension is unprofessional”. Especially when I see people then setup .htaccess rules to make their PHP scripts run behind URLs with .html extensions, because “it looks so much more professional”. As if using PHP or other server-side code is something to be ashamed of.

It’s just a URL. Descriptive URLs and having one page per path is helpful to SEO, but file extensions really don’t matter. You just build your website in a certain way with a file and URL structure that makes sense. No need to purposely obfuscate the structure of your site.

I wouldn’t setup my sites like this, but I’m also a big fan of using frameworks and handling routing from within PHP code, so my sites never have file extensions.

7 Likes

“Uhh ackshually, using .php in URLs is totally fine, and hiding it is just performative professionalism :pleading_face::backhand_index_pointing_right::backhand_index_pointing_left:
Bro, you sound like a soyjack white knight cuck defending the honor of localhost/index.php?route=cope.

Nobody’s “ashamed” of PHP — we’re just not out here treating .php like it’s a vintage wine. You don’t see people flexing .aspx or .jsp either. It’s not a personality trait, my guy.

You’re the type to call clean URLs “dishonest” and unironically gatekeep behind Apache configs from 2012. Meanwhile the rest of us moved on — routing, controllers, REST APIs, MVC, you know… modern development. But nah, you’re in the trenches fighting for .php like it’s the last airbender.

Keep your .php URLs if it helps you sleep at night, but don’t act like you’re the last sane man in web dev while everyone else is sipping the “professional” Kool-Aid. That’s not a principled stand — it’s just digital crust.

Now go write a thinkpiece about why hiding file extensions is “web gentrification” or some other Reddit-core take.

Please stop being passive aggressive. This forum should not be a place to demoralize people. Future posts will be flagged and removed without warning if you ignore me.

Still slightly off topic, the official PHP website keeps the extension in their URL: PHP: parse_url - Manual

7 Likes

Visited the site, well done project. Well designed with a very detailed review about the service. Try slipping a referral link or if is a school project then it’s done.

2 Likes

nah people in here dont want to throw their money to buy random domain to use mofh

Don’t need to buy a domain to use MOFH, you could use a subdomain from eu.org or freedns.afraid.org

4 Likes

freedns.afraid.org cant use for mofh, it require ns connect, not ip connect

Contact their admins to enable it or use a different subdomain provider that is short. You can get approved as long as the domain/subdomain looks good in IFN’s eyes.

4 Likes

Please do not share links that contains sensitive content for people with PTSD.