Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm trying to host a tiny website on my home server (Windows 2012) and I am using a domain hosted with no-ip.org.

That domain is forwarded to my server here at home, which is only hooked up to a simple DSL router, but people tell me that when browsing the site it is often (if not always) rejected, or simply would not load at all. Upon reloading and/or turning off the security warnings the site works as expected.

Bottom line is I'd like to authenticate my server somehow to allow the site to load without people having to mess with the browser settings.

I don't need or want SSL, much less pay for it. I'm just after some soft of "authenticity" that tells the browsers my site isn't "bad". How can I do this?

share|improve this question

closed as off-topic by mulaz, Greg Askew, Andrew B, EEAA, Jacob Mar 25 at 17:25

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions must be relevant to professional system administration. Server Fault is dedicated to professional system and network administrators. End user and enthusiast questions are off-topic (contact your system administrator or hire a professional to help you out). Please see the Help Center for more information." – mulaz, Greg Askew, Andrew B, EEAA, Jacob
If this question can be reworded to fit the rules in the help center, please edit the question.

    
Not to scare you off in any way, but ServerFault is a question and answer site for professional system and network administrators.. This setup doesn't sound very professional. Perhaps the sister site SuperUser is where you wanted to ask your question? –  MattBianco Mar 25 at 14:03

2 Answers 2

Trust is not something you can force upon others. If it was up to a site operator to declare whether they could be trusted or not, what would malicious parties do?

If I was on a dynamic-IP setting up a HTTP web site that I wanted to look "real", I would:

  • focus on the content, complying with standards, passing HTML validations
  • make sure all machines on your network are free from malware
  • buy a domain in a "normal" TLD
  • update the zone each time my IP would change
  • get an SSL certificate from StartCom.

And then consider moving to a cheap VPS, of course...

share|improve this answer

Well, here is something simple.

Do not host the site there.

Use Cloudflare to give the site a cloudflare IP, and cloudflare pulls the site from you.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.