domain/sezar.city
- Registration data
RDAP - DNS records
A, AAAA, MX, NS, TXT, CAA, SOA - Email policy
_dmarc - TLS certificate
port 443 - Website snapshot
HTTP - Comparing with history
whois.is archive
RDAPA, AAAA, MX, NS, TXT, CAA, SOA_dmarcport 443HTTPwhois.is archivesezar.city was registered in June 2025 with NameSilo, and is due to expire in June 2028. Its website was online at the last check, served from Fornex Hosting's network. Email for sezar.city is handled by sezar.city. The website presents it as ЖК «Сезар Сити» (жилой комплекс бизнес-класса).
Registered 1 year ago. The website responds, SPF is published, though DMARC is not and the certificate is trusted.
| Type | Value |
|---|---|
| A | 185.18.52.211 AS16003 · Fornex Hosting S.L. · ES |
| MX | 10 mail.sezar.city |
| NS | ns1.fornex.com |
| NS | ns2.fornex.com |
| NS | ns3.fornex.com |
| NS | ns4.fornex.com |
| TXT | v=spf1 +a +mx +ip4:185.18.52.167 ~all |
| SOA | ns1.fornex.com hostmaster.fornex.com 2766997193 |
A network is whoever runs the servers behind the address. With a CDN such as Cloudflare in front, that is the CDN, not the company hosting the site behind it.
Read from the homepage's code and server headers. Sites can hide what they use, so this list may be incomplete.
No public prices on the pages we read.
Every value is quoted from the page linked beside it. Read from 1 page.
First observation recorded. Every change from here on is preserved and shown here.
Most registries now keep the registrant's details private, and whois.is doesn't show them. sezar.city is registered through NameSilo. The website presents itself as ЖК «Сезар Сити»; that is the site's own claim, not a verified owner.
sezar.city was registered on 28 Jun 2025, making it 1 year old.
The registry lists 28 Jun 2028 as the expiry date, 585 days from now. Most domains renew automatically before then.
sezar.city's website is served from Fornex Hosting's network.
Email for sezar.city is handled by sezar.city, according to its MX records.
It was up when we last checked, 5 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.