domain/beerentals.ca
- 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 archivebeerentals.ca was registered in November 2026 with NameSilo Technologies, and is due to expire in November 2030. Its website was online at the last check, served from Truehost Cloud's network. Email for beerentals.ca is handled by Google. The website presents it as Bee Rentals Montréal (party rentals).
Based on what we observed, it was registered within the last year.
| Type | Value |
|---|---|
| A | 102.203.116.14 AS329278 · Truehost Cloud Limited · KE |
| MX | 1 smtp.google.com |
| NS | ns1.cloudoon.com |
| NS | ns2.cloudoon.net |
| NS | ns3.cloudoon.com |
| TXT | google-site-verification=AVmhfRx4n-kh_6XJtrMsyTqgssLNXJqt85nBgZFOxlM |
| TXT | v=spf1 +a include:_spf.google.com include:_spf.truehostcloud.com ~all |
| DMARC | v=DMARC1; p=none; rua=mailto:[email protected] |
| SOA | ns1.cloudoon.com root.das131.truehost.cloud 2026112007 |
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.
Most registries now keep the registrant's details private, and whois.is doesn't show them. beerentals.ca is registered through NameSilo Technologies. The website presents itself as Bee Rentals Montréal; that is the site's own claim, not a verified owner.
beerentals.ca was registered on 10 Nov 2026, making it 11 days old.
The registry lists 10 Nov 2030 as the expiry date, 1450 days from now. Most domains renew automatically before then.
beerentals.ca's website is served from Truehost Cloud's network.
Email for beerentals.ca is handled by Google, according to its MX records.
It was up when we last checked, 21 hours ago (20 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.