domain/bramtravel.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 archivebramtravel.com was registered in March 2026 with OwnRegistrar, and is due to expire in March 2027. Its website was online at the last check, served from Truehost Cloud's network. Email for bramtravel.com is handled by bramtravel.com. The website names Bram.com as the business behind it.
Registered 1 year ago. The website responds, SPF and DMARC are published and the certificate is trusted.
| Type | Value |
|---|---|
| A | 102.203.116.14 AS329278 · Truehost Cloud Limited · KE |
| MX | 0 bramtravel.com |
| NS | ns1.cloudoon.com |
| NS | ns2.cloudoon.net |
| NS | ns3.cloudoon.com |
| TXT | v=spf1 +a +mx +ip4:102.203.116.13 +ip4:102.203.116.14 +include:_spf.truehostcloud.com ~all |
| DMARC | v=DMARC1;p=quarantine;sp=quarantine;adkim=r;aspf=s;pct=100;fo=0;rf=afrf;ri=86400;rua=mailto:[email protected];ruf=mailto:[email protected] |
| SOA | ns1.cloudoon.com root.das131.truehost.cloud 2026111801 |
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. bramtravel.com is registered through OwnRegistrar. The website presents itself as Bram.com; that is the site's own claim, not a verified owner.
bramtravel.com was registered on 18 Mar 2026, making it 8 months old.
The registry lists 18 Mar 2027 as the expiry date, 117 days from now. Most domains renew automatically before then.
bramtravel.com's website is served from Truehost Cloud's network.
Email for bramtravel.com is handled by bramtravel.com, according to its MX records.
It was up when we last checked, 4 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.