I'm going to guess folk with this issue are leaving off the protocol. Look at the `Location` header you get back if you've asked to shorten example.com (which displays this issue) vs https://example.com (which doesn't).