u/Safe_Mission_3524

I have been seeing a lot of survey sites being recommended but not sure if they are reliable. Which ones do you use and how much are you earning from it? Thank you!

I have been in the web hosting industry for more than 10 years and have dealt with a lot of different issues. Some absolutely important ones are what many people miss and I hope this helps at least some of you.

1. If you are planning to purchase a new domain and host it, always create a free cloudflare account and add the domain name to cloudflare, keep the proxy (orange cloud) enabled by default. Even if you have not purchased the domain yet, cloudflare still allows you to add a new domain. Once added and proxy enabled, update your nameservers to point to cloudflare directly.

This way, when you update the dns records to point for your server, your actual server IP becomes private/hidden from day 1 and the no of bot/spam traffic coming to your site will be significantly reduced.

Some bots directly access your site using your server IP by checking for historical dns entries and try to perform attacks and such instances will be reduced significantly.

There are still other ways a determined attacker can get your server IP from your mx or spf record but most spammy bots do not go to that extent, so the attack surface is very low.

2. Always use cloudflare and its cdn/proxy from day one when your site goes online. This way, cf can learn about the incoming traffic and block malicious and spammy bots regularly. This would prevent you from enabling their under attack mode when an actual ddos attack happens on your site in the future.

3. never rely completely on server side backups even if you are paying more money for a better server. Sometimes even if there is no fault from the hosting provider, the backup/restore softwares they use can sometimes act up and your data may not be backed up successfully all the time. Always take your own backups regularly and store it safely in your pc or an external hard drive/google cloud etc.

4. If you accidentally deleted some dns records, you can almost always find the historical dns entries for your domain in sites like security trails, dnshistory dot org etc. just search google for "historical dns check" and you'll see many sites who had scraped your dns records in the past. This is one way an attacker can get your IP as explained in step 1.

5. For better email deliverability of emails from your site's contact forms/e-commerce order related email notifications to your customers, always use a proper SMTP service instead of using the default php mailer as most receiving email servers reject or mark those emails as spam if the sender doesn't use SMTP.

6. if your site's data and its backup is completely deleted, most of the times you can find snapshots of your site at archive.org. You can refer to different snapshots and rebuild your site. Even though this is a tedious task, you will start with at least something instead of nothing. This is why regular offline backups are important (read step 3).

7. Always keep your site's plugins, themes, scripts updated to support their latest versions. Site compromises almost always happens due to an attacker finding vulnerabilities on outdated softwares.

8. Don't install nulled/cracked plugins from sites offering them for a very cheap price. You never know what's hidden in them and many times, they are the root causes of site compromises. If you cannot afford to pay for premium plugins or themes, ask claude to help you build your own plugin and theme specifically designed for your site and ask it to make it as secure as possible to prevent from any attacks.

Build this plugin or theme in a seperate project and regularly ask claude to check for any vulnerabilities based on latest news and ask it to keep updating them and then install the updated version to your site.

Cheers!

I have been in the web hosting industry for more than 10 years and have dealt with a lot of different issues. Some absolutely important ones are what many people miss and I hope this helps at least some of you.

1. If you are planning to purchase a new domain and host it, always create a free cloudflare account and add the domain name to cloudflare, keep the proxy (orange cloud) enabled by default. Even if you have not purchased the domain yet, cloudflare still allows you to add a new domain. Once added and proxy enabled, update your nameservers to point to cloudflare directly.

This way, when you update the dns records to point for your server, your actual server IP becomes private/hidden from day 1 and the no of bot/spam traffic coming to your site will be significantly reduced.

Some bots directly access your site using your server IP by checking for historical dns entries and try to perform attacks and such instances will be reduced significantly.

There are still other ways a determined attacker can get your server IP from your mx or spf record but most spammy bots do not go to that extent, so the attack surface is very low.

2. Always use cloudflare and its cdn/proxy from day one when your site goes online. This way, cf can learn about the incoming traffic and block malicious and spammy bots regularly. This would prevent you from enabling their under attack mode when an actual ddos attack happens on your site in the future.

3. never rely completely on server side backups even if you are paying more money for a better server. Sometimes even if there is no fault from the hosting provider, the backup/restore softwares they use can sometimes act up and your data may not be backed up successfully all the time. Always take your own backups regularly and store it safely in your pc or an external hard drive/google cloud etc.

4. If you accidentally deleted some dns records, you can almost always find the historical dns entries for your domain in sites like security trails, dnshistory dot org etc. just search google for "historical dns check" and you'll see many sites who had scraped your dns records in the past. This is one way an attacker can get your IP as explained in step 1.

5. For better email deliverability of emails from your site's contact forms/e-commerce order related email notifications to your customers, always use a proper SMTP service instead of using the default php mailer as most receiving email servers reject or mark those emails as spam if the sender doesn't use SMTP.

6. if your site's data and its backup is completely deleted, most of the times you can find snapshots of your site at archive.org. You can refer to different snapshots and rebuild your site. Even though this is a tedious task, you will start with at least something instead of nothing. This is why regular offline backups are important (read step 3).

7. Always keep your site's plugins, themes, scripts updated to support their latest versions. Site compromises almost always happens due to an attacker finding vulnerabilities on outdated softwares.

8. Don't install nulled/cracked plugins from sites offering them for a very cheap price. You never know what's hidden in them and many times, they are the root causes of site compromises. If you cannot afford to pay for premium plugins or themes, ask claude to help you build your own plugin and theme specifically designed for your site and ask it to make it as secure as possible to prevent from any attacks.

Build this plugin or theme in a seperate project and regularly ask claude to check for any vulnerabilities based on latest news and ask it to keep updating them and then install the updated version to your site.

Cheers!

I have been in the web hosting industry for more than 10 years and have dealt with a lot of different issues. Some absolutely important ones are what many people miss and I hope this helps at least some of you.

1. If you are planning to purchase a new domain and host it, always create a free cloudflare account and add the domain name to cloudflare, keep the proxy (orange cloud) enabled by default. Even if you have not purchased the domain yet, cloudflare still allows you to add a new domain. Once added and proxy enabled, update your nameservers to point to cloudflare directly.

This way, when you update the dns records to point for your server, your actual server IP becomes private/hidden from day 1 and the no of bot/spam traffic coming to your site will be significantly reduced.

Some bots directly access your site using your server IP by checking for historical dns entries and try to perform attacks and such instances will be reduced significantly.

There are still other ways a determined attacker can get your server IP from your mx or spf record but most spammy bots do not go to that extent, so the attack surface is very low.

2. Always use cloudflare and its cdn/proxy from day one when your site goes online. This way, cf can learn about the incoming traffic and block malicious and spammy bots regularly. This would prevent you from enabling their under attack mode when an actual ddos attack happens on your site in the future.

3. never rely completely on server side backups even if you are paying more money for a better server. Sometimes even if there is no fault from the hosting provider, the backup/restore softwares they use can sometimes act up and your data may not be backed up successfully all the time. Always take your own backups regularly and store it safely in your pc or an external hard drive/google cloud etc.

4. If you accidentally deleted some dns records, you can almost always find the historical dns entries for your domain in sites like security trails, dnshistory dot org etc. just search google for "historical dns check" and you'll see many sites who had scraped your dns records in the past. This is one way an attacker can get your IP as explained in step 1.

5. For better email deliverability of emails from your site's contact forms/e-commerce order related email notifications to your customers, always use a proper SMTP service instead of using the default php mailer as most receiving email servers reject or mark those emails as spam if the sender doesn't use SMTP.

6. if your site's data and its backup is completely deleted, most of the times you can find snapshots of your site at archive.org. You can refer to different snapshots and rebuild your site. Even though this is a tedious task, you will start with at least something instead of nothing. This is why regular offline backups are important (read step 3).

7. Always keep your site's plugins, themes, scripts updated to support their latest versions. Site compromises almost always happens due to an attacker finding vulnerabilities on outdated softwares.

8. Don't install nulled/cracked plugins from sites offering them for a very cheap price. You never know what's hidden in them and many times, they are the root causes of site compromises. If you cannot afford to pay for premium plugins or themes, ask claude to help you build your own plugin and theme specifically designed for your site and ask it to make it as secure as possible to prevent from any attacks.

Build this plugin or theme in a seperate project and regularly ask claude to check for any vulnerabilities based on latest news and ask it to keep updating them and then install the updated version to your site.

Cheers!

I currently smoke but don't drink and it's the only thing keeping me away searching for a partner. I don't know how girls react to it and if they tell their parents about this after rejection. I have kept this a secret from my own parents for some years. For people asking to quit, i have tried it many times without luck. Thanks!

I was working on a complex issue which fable 5 troubleshooted after a long session. I asked it to create a detailed question without giving a lot of context I did for fable. Then I created a new chat under each model and asked the same question.

Results ranked:

1st - Opus 5

2nd - Fable 5

3rd - Opus 4.6

4th - Sonnet 4.6

5th - Opus 4.8

6th - Opus 4.7

Opus 5 also consumed a little less usage than opus 4.8 but opus 5's result was a lot better.

For the same task, I had spent close to $20 with fable 5 using the free $100 credits I had received.

Opus 5 is very promising and I hope Anthropic keeps it the same way.

I was working on a complex issue which fable 5 troubleshooted after a long session. I asked it to create a detailed question without giving a lot of context I did for fable. Then I created a new chat under each model and asked the same question.

Results ranked:

1st - Opus 5

2nd - Fable 5

3rd - Opus 4.6

4th - Sonnet 4.6

5th - Opus 4.8

6th - Opus 4.7

Opus 5 also consumed a little less usage than opus 4.8 but opus 5's result was a lot better.

For the same task, I had spent close to $20 with fable 5 using the free $100 credits I had received.

Opus 5 is very promising and I hope Anthropic keeps it the same way.

Fable is still available for normal chats but is no longer available in claude code or cowork.

If you wanted to get things done with cowork or code, just create a new project and a new chat in the web interface, give all of your requirements and let fable do the planning. Ask it to plan based on how opus or sonnet do the tasks.

Open a different model in cowork or code and give the instructions.md file and let it work on your tasks. Personally I would use opus 4.6 as it's still the best in for my use cases. The fact that fable 5 is still available for chats is the only reason I am still with claude.

Edit - it's gone now, lol

I have used this plugin on many occasions and it definitely gets the job done but their sneaky marketing tactics about server upload limit is something I wanted to get it off of my chest.

The free plugin says it's the server/cPanel upload limit restricting it to restore a large file above 2GB but even if all of the server side limits are reached, it still throws errors. As soon as I use the pro version, everything starts working suddenly. I have confirmed that it's not anything related to server side firewall/waf/modsecurity etc. even their product page says it's due to server side restrictions. Has anyone else observed this as well? I have worked on hundreds of site restorations and this really annoys me all the time I use the free plugin. Why not just say to the users that we need to upgrade to remove the restrictions?

I have used this plugin on many occasions and it definitely gets the job done but their sneaky marketing tactics about server upload limit is something I wanted to get it off of my chest.

The free plugin says it's the server/cPanel upload limit restricting it to restore a large file above 2GB but even if all of the server side limits are reached, it still throws errors. As soon as I use the pro version, everything starts working suddenly. I have confirmed that it's not anything related to server side firewall/waf/modsecurity etc. even their product page says it's due to server side restrictions. Has anyone else observed this as well? I have worked on hundreds of site restorations and this really annoys me all the time I use the free plugin. Why not just say to the users that we need to upgrade to remove the restrictions?

Since fable usage has been reset, this is what I am doing.

1. Open all of your projects folder and see which one is worth to continue or finish building first.

2. Prioritize the first one or two projects which has the maximum potential to go big.

3. Ask fable in the max or extended thinking mode (depending on how large your project is) to come up with a build-plan.md file with everything that has happened so far and what features you need, bug fixes etc. Specifically tell it that you would continue building the project using opus 4.6 or 4.8 and come up with the best way even lower llms can understand and implement all the tasks or bug fixes.

Every model can code if given proper instructions. Fable5 is excellent in creating a detailed and thoughtful plan. Don't use it to build it you have a very large project with a lot of features. You would need a backup plan incase you run out of credits midway.

4. Publish your first two projects before 12th July so that you can fix any bugs in production using fable.

5. In claude code, inside the readme.md file, ask it to always refer to the build-plan.md file which fable has created.

And good luck with your projects🤞

If you are visiting bangalore for the first time or already living here coming from other states:

1. Never take autos or cabs directly near the bus/railway station. Always walk for 100 meters if you can and book it from uber. Never ola or rapido. If you have luggage, book it while you are in the bus/train 5 mins before your arrival.

2. Try to learn at least a few basic words in kannada like anna, change illa (no change), (put area name) ge bartira? while trying to catch a local auto. Chances of you getting scammed is very less.

3. Find a reputable broker from an actual firm who can understand your language if you are renting a house. Don't go with local brokers.

4. Use BMTC buses as much as possible. It's simply the best transport system.

5. Never ever take the bridge in majestic during late nights and early mornings to reach a particular BMTC bus platform. Always go from the ground. You will save a lot of money and harassment from transgenders and beggars who target in bulk when you take the bridge as it's shorter than walking downstairs.

6. Always keep at least 200-300 rupees in cash at least while taking an auto. You'll save a lot of headache from drivers who only need cash.

7. If you can afford a water purifier, go for it even if you are planning to stay for a few months. You can go with subscription based ones. There are many. Else, the best thing is to go and get the water from 5rs water centers which are all over bangalore and the quality is a lot better than purifier water.

8. Never ever drink tap water directly. Tds levels in Bangalore are crazy high.

For everyone else:

1. Get your water tanks cleaned at home including the sump at least once in a year.

2. Clean your washing machines using scale removers every 3-6 months.

3. Clean your kitchen and bathroom drains every 1-3 months using drain cleaners which will melt the hairs and other things stuck. This will be a lifesaver and prevents floodings or blocked drainage.

4. Get a water tds machine - costs just 200 rs. It will show you if your home/purifierwater is good for drinking or cooking or even showering if you have dandruff or hairloss problems.

5. Don't go with paid anti virus or anti malware tools like Kaspersky, avast etc. windows defender is the best one and comes free for all windows machines.

6. instead of drilling a lot of holes on the walls for various purposes, get double tape hooks. This will save you money when you are vacating and avoids a lot of hassles with the landlord.

I guess that's it. If you want know more about anything else, I'll be happy to answer.

Has anyone here were able to combat spoofed emails sent from your own address if the domain is using cPanel?

I understand that the domain has to be properly authenticated with spf, dkim, dmarc and bimi(as an extra security). Respectfully , I also am not looking for any advice on using external services such as Google workspace or O365 because I know they are really good at combating such spam.

I understand about training email filters or spam assassin to combat spam for incoming emails but the problem with spoofing is, anyone can simply modify the header to be abc@example.com to send it to abc@example.com from any IP or a cheap vps or from hacked sites.

This question is mainly for cPanel users who were able to successfully combat spoofing. I am working in the web hosting/sysadmin field from past 8 years but haven't been able to figure this out. I never had root access though.

Reporting sender IPs/domains to third party hosting providers is a nightmare in itself and takes up a lot of time.

Is there any setting in WHM or through root ssh access wherein if an email was sent from the same address, before delivering that message, cPanel performs the sending IP/domain/header checks and block such emails automatically?

Please do not bash me here because even though I have worked in this field for many years, I never had root access and looking at exim configurations, I am a bit scared to make any changes on my test vps running cPanel to break more email functionality.

I also know that we can use incoming email filters or third party inbound relay services like barracuda but I mainly want to know if there is any way I can protect the accounts from spoofing on a cPanel which doesn't use any kind of inbound spam filters.

Pros in this sub, have you found a way to combat this? Would really appreciate all of the helpful comments.