Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://oldbytes.space/@drscriptt" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>drscriptt</span></a></span> Naive question: <em>WHEN</em> does the average <a href="https://infosec.space/tags/Internet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Internet</span></a> <a href="https://infosec.space/tags/user" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>user</span></a> ever open up a webpage with an <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IP</span></a> address instead of a <a href="https://infosec.space/tags/domain" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>domain</span></a> or even <a href="https://infosec.space/tags/FQDN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FQDN</span></a>?</p><ul><li>Seriously, the only cases I saw were either some old, non-public - facing server in some B2B/API setting <em>or</em> a test that <a href="https://infosec.space/tags/httpd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>httpd</span></a> / <a href="https://infosec.space/tags/ngnix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ngnix</span></a> / <a href="https://infosec.space/tags/ssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ssh</span></a> / … function properly on like a <a href="https://infosec.space/tags/VPS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VPS</span></a> and that the <a href="https://infosec.space/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DNS</span></a> hasn't been updated (yet!) to include said host / FQDN in the records, and even then it's <em>bad</em> cuz you'd rather want to use it's FQDN instead because with <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> shortages on one hand and tools like <a href="https://infosec.space/tags/Portainer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Portainer</span></a> on the other, one should not use an <a href="https://infosec.space/tags/IPaddress" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPaddress</span></a> as addressing method because <a href="https://infosec.space/tags/WAF" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WAF</span></a> / <a href="https://infosec.space/tags/Proxies" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Proxies</span></a> used to <em>"<a href="https://infosec.space/tags/MUX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MUX</span></a>"</em> / <em>"<a href="https://infosec.space/tags/NAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT</span></a>"</em> services under one IP address or <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> block may need that distinction by being queried for a specific FQDN... </li></ul><p>The Idea if !SSL / <a href="https://infosec.space/tags/TLD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TLD</span></a> for <a href="https://infosec.space/tags/IPaddresses" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPaddresses</span></a> makes me <a href="https://www.youtube.com/watch?v=g3j9muCo4o0" rel="nofollow noopener" target="_blank">feel like Jeff Goldblum!</a></p>