Dev Stack Source

Answer : First Go to Settings in Postman : Off the SSL certificate verification in General Tab: Off the Global Proxy Configuration and Use System Proxy in Proxy Tab: Make Request Timeout to 0 (Zero) I had the same issue. It was caused by a newline at the end of the "Authorization" header's value, which I had set manually by copy-pasting the bearer token (which accidentally contained the newline at its end) If you get a "Could not get any response" message from Postman native apps while sending your request, open Postman Console (View > Show Postman Console), resend the request and check for any error logs in the console. Thanks to numaanashraf

Answer : Most answers given here are false . It is perfectly legal to have an underscore in a domain name. Let me quote the standard, RFC 2181, section 11, "Name syntax": The DNS itself places only one restriction on the particular labels that can be used to identify resource records. That one restriction relates to the length of the label and the full name. [...] Implementations of the DNS protocols must not place any restrictions on the labels that can be used. In particular, DNS servers must not refuse to serve a zone because it contains labels that might not be acceptable to some DNS client programs. See also the original DNS specification, RFC 1034, section 3.5 "Preferred name syntax" but read it carefully. Domains with underscores are very common in the wild. Check _jabber._tcp.gmail.com or _sip._udp.apnic.net . Other RFC mentioned here deal with different things. The original question was for domain names . If the question is for...