domain/bharatglitz.com
- 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 archivebharatglitz.com was registered in March 2009 with GoDaddy.com, and is due to expire in March 2027. Its website was online at the last check, served from HostBet Cloud Technologies Private's network. bharatglitz.com doesn't receive email: it publishes no mail servers. The website presents it as BharatGlitz (entertainment news and cinema website).
Registered 18 years ago. The website responds, DMARC is published, though SPF is not and the certificate is trusted.
| Type | Value |
|---|---|
| A | 86.107.77.36 AS216395 · HostBet Cloud Technologies Private Limited · NL |
| NS | ns49.domaincontrol.com |
| NS | ns50.domaincontrol.com |
| DMARC | v=DMARC1; p=quarantine; adkim=r; aspf=r; rua=mailto:[email protected]; |
| SOA | ns49.domaincontrol.com dns.jomax.net 2026102502 |
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 4 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. bharatglitz.com is registered through GoDaddy.com. The website presents itself as BharatGlitz; that is the site's own claim, not a verified owner.
bharatglitz.com was registered on 8 Mar 2009, making it 17 years old.
The registry lists 8 Mar 2027 as the expiry date, 107 days from now. Most domains renew automatically before then.
bharatglitz.com's website is served from HostBet Cloud Technologies Private's network.
No one: bharatglitz.com publishes no MX records, so it can't receive email.
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.