domain/rhga.pro
- 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 archiverhga.pro was registered in December 2014 with RU-CENTER, and is due to expire in December 2026. Its website was online at the last check, served from JSC _Severen-Telecom_'s network. rhga.pro doesn't receive email: it publishes no mail servers. The website presents it as ЭИОС РХГА (electronic information and educational environment).
Based on what we observed, its registration expires in 26 days and it publishes no email authentication records.
| Type | Value |
|---|---|
| A | 195.182.133.61 AS6858 · JSC _Severen-Telecom_ · RU |
| NS | ns3-l2.nic.ru |
| NS | ns4-cloud.nic.ru |
| NS | ns4-l2.nic.ru |
| NS | ns8-cloud.nic.ru |
| NS | ns8-l2.nic.ru |
| SOA | ns3-l2.nic.ru dns.nic.ru 2015031839 |
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 2 pages.
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. rhga.pro is registered through RU-CENTER. The website presents itself as ЭИОС РХГА; that is the site's own claim, not a verified owner.
rhga.pro was registered on 17 Dec 2014, making it 11 years old.
The registry lists 17 Dec 2026 as the expiry date, 26 days from now. Most domains renew automatically before then.
rhga.pro's website is served from JSC _Severen-Telecom_'s network.
No one: rhga.pro publishes no MX records, so it can't receive email.
It was up when we last checked, 3 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.