Thanks, I see it too. Let me dig!
Shadow
lol yeah i saw that as soon as i posted, so i deleted mine =)
Yay!
They should be able to still recover the domain. From the top of the page "To renew this domain, please sign in to your Sav.com Account".
Just off whois on linux, but I'm not clear why it lists two different sets of dates. I'm guessing querying the root whois vs the registrar, and hexbear is currently in the process of fixing their domain which is why one set is 2026.
~$ whois hexbear.net
Domain Name: HEXBEAR.NET
Registry Domain ID: 2584175083_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois-service.virtualcloud.co
Registrar URL: http://sav.com/
Updated Date: 2025-02-11T17:34:08Z
Creation Date: 2021-01-12T00:35:22Z
Registry Expiry Date: 2026-01-12T00:35:22Z
>>> Last update of whois database: 2025-02-11T20:42:41Z <<<
*snip*
Domain Name: HEXBEAR.NET
Registry Domain ID: 2584175083_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois-service.virtualcloud.co
Registrar URL: https://www.sav.com/
Updated Date: 2025-02-11T17:35:29Z
Creation Date: 2021-01-12T00:35:25Z
Registrar Registration Expiration Date: 2025-01-12T00:35:22Z
Registrar: SAV.COM, LLC
*snip*
>>> Last update of WHOIS database: 2025-02-11T17:35:29Z <<<
Unless the +1 year date is the registrar holding it for themselves to auction off, which seems equally likely.
DNS caching at play. The registrar has pointed it to their own nameservers, and that gets cached in lots of places.
Their domain expired a month ago, this is pretty normal for a registrar to do with expired domains.
Updated Date: 2025-02-11T17:35:29Z
Creation Date: 2021-01-12T00:35:25Z
Registrar Registration Expiration Date: 2025-01-12T00:35:22Z
With the way the bricks are laid, wouldn't it distribute the weight across the entire base?
Can you link me to an example please? Pictrs has been giving me troubles, but everything should be working now.
Fixed now!
Fixed now