Impending Doom!
monitoring the Domain registration and SSL cert expiration time for top one million websites
behance.net
Expiry
| 🔒 Certificate Expiry | in 14 days | |
| 🌐 Registration Expiry | in 336 days | |
| Last Check | Nov 27 '23 at 03:49 | |
Ping
| Status Code | 301 | |
| Response | 379ms | |
| Last Check | Dec 01 '23 at 12:05 | |
Headers
| accept-ranges | bytes |
| alt-svc | h3=":443";ma=86400,h3-29=":443";ma=86400,h3-27=":443";ma=86400 |
| connection | close |
| content-length | 0 |
| date | Fri, 01 Dec 2023 12:03:58 GMT |
| location | https://www.behance.net/ |
| retry-after | 0 |
| server | Varnish |
| via | 1.1 varnish |
| x-cache | MISS |
| x-cache-hits | 0 |
| x-served-by | cache-sof1510038-SOF |
| x-timer | S1701432239.744032,VS0,VE0 |
API
😱 Expiring Domains
🔥 Expired Domains
GET /api/v1/domains/expiredOptional: ?top=n (default 1000)
Query by Expiry Date
GET /api/v1/domains?from={DATE}&to={DATE}
🎲 Domain Roulette
FAQ
How often do you check for update?
Sites are checked once every 7 days or daily if near expiry.
What is the tech stack behind this?
This site and all its componenets are written entirely in 🦀 Rust.
It uses sqlx to access the Postgres database, askama for templating
and classless.de for class-less UI that is blazing fast to load.
Top one million domains are sourced from The Majestic Million and are periodically updated.
..but WHY?
Because I needed to play with Rust's safe and "correct" concurrency features. The process that loads domain from majestic and check for SSL cert heavily uses concurrent threads. This frontned is server side rendered page instead of an SPA because I wanted to try out the state of Rust templating.
The result is brilliant! it uses so little resources that I can keep supporting this service for as long as possible. If you decide to use the API for serious purpose then you can contact me.