domain/intimatefaithministry.org
- 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 archiveintimatefaithministry.org was registered in August 2022 with NameSilo, and is due to expire in August 2027. Its website was online at the last check, served from Amazon.com's network. intimatefaithministry.org doesn't receive email: it publishes no mail servers. The website presents it as Intimate Faith Ministry (church).
Based on what we observed, it publishes no email authentication records.
| Type | Value |
|---|---|
| A | 64.29.17.1 AS16509 · Amazon.com, Inc. · US |
| A | 64.29.17.65 AS16509 · Amazon.com, Inc. · US |
| NS | ns1.vercel-dns.com |
| NS | ns2.vercel-dns.com |
| CAA | 0 issue "letsencrypt.org" |
| CAA | 0 issue "pki.goog" |
| CAA | 0 issue "sectigo.com" |
| SOA | ns1.vercel-dns.com hostmaster.nsone.net 1779032523 |
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 3 pages.
Most registries now keep the registrant's details private, and whois.is doesn't show them. intimatefaithministry.org is registered through NameSilo. The website presents itself as Intimate Faith Ministry; that is the site's own claim, not a verified owner.
intimatefaithministry.org was registered on 28 Aug 2022, making it 4 years old.
The registry lists 28 Aug 2027 as the expiry date, 281 days from now. Most domains renew automatically before then.
intimatefaithministry.org's website is served from Amazon.com's network.
No one: intimatefaithministry.org 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.