domain/stoneandtimberbuilders.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 archivestoneandtimberbuilders.com was registered in December 2024 with WebNic.cc, and is due to expire in December 2026. Its website was online at the last check. Email for stoneandtimberbuilders.com is handled by stoneandtimberbuilders.com.
Based on what we observed, its registration expires in 20 days.
| Type | Value |
|---|---|
| A | 51.68.131.131 |
| MX | 0 stoneandtimberbuilders.com |
| NS | ns1.cloudoon.com |
| NS | ns2.cloudoon.net |
| NS | ns3.cloudoon.org |
| TXT | v=spf1 +a +mx 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.pld111.truehost.cloud 2026092701 |
We couldn't place this site's addresses on a network.
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.
We didn't recognise any technology on the homepage.
None stated on the pages we read.
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. stoneandtimberbuilders.com is registered through WebNic.cc.
stoneandtimberbuilders.com was registered on 11 Dec 2024, making it 1 year old.
The registry lists 11 Dec 2026 as the expiry date, 20 days from now. Most domains renew automatically before then.
Email for stoneandtimberbuilders.com is handled by stoneandtimberbuilders.com, according to its MX records.
It was up when we last checked, 6 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.