https/http URLs for the services:
http or https may be use with their respective default ports 80 and 443,
domain names that may be used:

• www.balug.org (dual stack: this service available via IPv4 and IPv6)
  
• www.ipv4.balug.org (this service available only via IPv4)
  
• www.ipv6.balug.org (this service available only via IPv6)
  

Note that in the above, if the www. prefix is omitted, will HTTP redirect to include the www. prefix.
Path portion of URL/URI:
/myip
So, e.g:
https://www.balug.org/myip http://www.balug.org/myip
https://www.ipv4.balug.org/myip http://www.ipv4.balug.org/myip
https://www.ipv6.balug.org/myip http://www.ipv6.balug.org/myip

domain names that may be used:

• balug.org (dual stack: this service available via IPv4 and IPv6)
  
• ipv4.balug.org (this service available only via IPv4)
  
• ipv6.balug.org (this service available only via IPv6)
  

Note that the above may optionally be prefixed by www.
user / login name, use myip, e.g. ssh -T myip@balug.org or ssh -l myip -T balug.org
There is no password and password is neither needed nor requested.
pseudo-terminal allocation will not occur, so may want to use -T option or equivalent option/setting
ssh fingerprints, see DNSSEC secured DNS SSHFP records, for many clients, may also be able to use, e.g.:
ssh -T -o VerifyHostKeyDNS=yes myip@balug.org
One may also want to put suitable configuration options in ~/.ssh/config or equivalent, e.g.:

Host balug.org balug.org. *.balug.org *.balug.org.
User myip
RequestTTY no
VerifyHostKeyDNS yes

so one can then conveniently do something like just: ssh balug.org
The command is forced, so any command(s) specified to/via ssh are ignored.