Let's say I have a website - example.com. If I create a binding in IIS, with *.example.com then abc.example.com works.

However, abc.in.example.com doesn't work. It gives me 404 status code.

Any suggestions.

  • 1
    Is: "Learn how wildcards work" a valid answer for you? Because you expect things to work that are explicitly not working by standards.
    – TomTom
    Jan 23 at 9:55
  • @TomTom Not sure. If one only knew how it worked, there wouldn't be this question.
    – Tushar
    Jan 24 at 8:34
  • Yeah, but rtfm is not really optional. It is clear in any documentation i ever read that wildcards are ONE LEVEL ONLY and do not extend downwards.
    – TomTom
    Jan 24 at 9:30

1 Answer 1


This is how wildcard certificates work. *.example.com work only for hosts like: host1.example.com, host2.example.com, etc.

If you want to have it work for abc.in.example.com you need to use certificate for *.in.example.com

The same is situation with binding to wildcard hosts.

  • 1
    Thanks @RomeoNinov for your answer. That worked for me.
    – Tushar
    Jan 24 at 8:33
  • @Tushar, if you are happy with my answer feel free to accept it (tick on the left side of the answer) :) Jan 24 at 9:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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