domain/falter.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 archivefalter.com was registered in January 1996 with Network Solutions, and is due to expire in January 2027. Its website was online at the last check, served from Newfold Digital's network. Email for falter.com is handled by falter.com. The website presents it as falter.com (website).
Registered 31 years ago. The website responds, SPF is published, though DMARC is not and the certificate is trusted.
| Type | Value |
|---|---|
| A | 65.254.227.224 AS29873 · Newfold Digital, Inc. · US |
| MX | 30 mx.falter.com |
| NS | ns1.powweb.com |
| NS | ns2.powweb.com |
| TXT | v=spf1 ip4:38.113.1.0/24 ip4:38.113.20.0/24 ip4:65.254.224.0/19 include:websitewelcome.com ?all |
| SOA | ns1.powweb.com dnsadmin.powweb.com 2006062121 |
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. falter.com is registered through Network Solutions. The website presents itself as falter.com; that is the site's own claim, not a verified owner.
falter.com was registered on 18 Jan 1996, making it 30 years old.
The registry lists 19 Jan 2027 as the expiry date, 59 days from now. Most domains renew automatically before then.
falter.com's website is served from Newfold Digital's network.
Email for falter.com is handled by falter.com, according to its MX records.
It was up when we last checked, 20 hours ago (21 Nov 2026), answering with HTTP 200. That shows how it was then, not a guarantee of right now.