Sending Bitcoin to IP addresses is no longer possible.

--Knight Hider

There are some things that are no longer possible because they were removed. The first is to be sending to IP address which people on this forum and other bitcoin users have used befor, but this is not secure like sending directly to your bitcoin address. The other one that is possible before was to send to public key, but it is not possible again. The only way you can now send bitcoin is only through the use of bitcoin address.

I can recall that this topic was made before even though i might have answers on that topic too. Well, here is mine, IP should be secure like there are many layers on internet and only the experienced ones or the most careful ones will use the IP in only severe conditions and if they would have used then they must have secured the connection first. As, i think it must not be a preferred way back then well that's what i assumed from this because many legendary members are so careful in such cases.

So, the best practice must be sending on Wallet address instead of IP where both parties have to be online while making the transaction.

You do not need to try anything like that, P2PK was used before bitcoin address was created which was P2PKH, which means you will pay to public key hash which is bitcoin address, instead of paying to public key directly. There are now other address types that can be used for payment which is what you should better be using.

If you want to use P2PK, then at least use compressed key. For example:
Also, instead of P2PK, you could switch to Taproot, then Schnorr signatures will be applied, and nobody will know, how many keys were aggregated.

Thank you very much. I have looked for old transactions and found such type of address. E.g. Hal’s one: 0411db93e1dcdb8a016b49840f8c53bc1eb68a382e97b1482ecad7b148a6909a5cb2e0eaddfb84c cf9744464f82e160bfa9b8b64f9d4c03f999b8643f656b412a3

Mempool.space still considers these symbols as a legitimate Bitcoin address.

P2PK is still standard and block explorers should still identify them as such. Some of the block explorers erroneously identify them as a P2PKH address type instead which is wrong. Interestingly, Bitcoin addresses were used for receiving payments from the start but Pay-To-IP feature and mining both uses P2PK instead. Hence, Hal Finney transaction could just be using Pay-To-IP.

Hmm... When I type this public key in their search field, they find it as an address.

The search bar part, yeah, incorrect, but they've indeed distinguished it from other standard outputs like P2PKH, which is enough for me.

Well, yes, but why not showing you the balance of that particular public key? You can argue the same for P2PKH, that we're talking about a specific script that contains the RIPEMD-160 hash.

It is entirely possible that it's just buggy and they're too lazy to fix it.
It could be that based on their search request history they came to the conclusion that some users are indeed using their public key to check their balance. But considering that in today's available wallet softwares addresses are used not P2PK, they convert that pubkey to different address types and the website is redirected to the first one that has been used otherwise show the default one which is P2PKH.
The bug is where their indexed database counts balance in P2PK outputs as the P2PKH balance.