connectusfund.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 88 days left18 years oldTranco #429056
70
connectusfund.org was registered on 21 Apr 2008 via GoDaddy.com, LLC and the registry expiry is 21 Apr 2028. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/connectusfund.org.
connectusfund.org publishes 2 nameservers. DNSSEC is not signed.
connectusfund.org has 2 IPv4 addresses (188.114.96.4, 188.114.97.4) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.4 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 88 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Google Analytics, HTTP/3, Mediavine, MySQL, PHP, Super Page Cache, WordPress and jQuery. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for connectusfund.org in the checks that ran.
Domain · RDAP/WHOIS
connectusfund.org was registered on 21 Apr 2008 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/connectusfund.org.
| Registered | since 21 Apr 2008 |
|---|---|
| Created | 21 April 2008 |
| Updated | 12 August 2026 |
| Expires | 21 April 2028 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | bella.ns.cloudflare.com, greg.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/connectusfund.org |
connectusfund.org carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
connectusfund.org carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
connectusfund.org carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
connectusfund.org carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver bella.ns.cloudflare.com is published for connectusfund.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/connectusfund.org.
Nameserver greg.ns.cloudflare.com is published for connectusfund.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/connectusfund.org.
DNS
connectusfund.org has 4 address records, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.4, 188.114.97.4 |
|---|---|
| AAAA | 2a06:98c1:3120::3, 2a06:98c1:3121::3 |
| NS | bella.ns.cloudflare.com, greg.ns.cloudflare.com |
| MX | mx00.1and1.com (10), mx01.1and1.com (10) |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 188.114.96.4 answers for connectusfund.org at resolver 1.1.1.1:53.
IPv4 address 188.114.97.4 answers for connectusfund.org at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for connectusfund.org at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for connectusfund.org at resolver 1.1.1.1:53.
Mail exchanger mx00.1and1.com has preference 10.
Mail exchanger mx01.1and1.com has preference 10.
Hosting and geo
connectusfund.org is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.4 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for connectusfund.org is valid, with 88 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | connectusfund.org |
| Valid from | 29 October 2026 |
| Valid until | 27 January 2027 |
| Days left | 88 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.connectusfund.org, connectusfund.org.
Tech stack
Tech detection checked the fetched homepage and named 9 products. Source: wappalyzergo.
- Cloudflare · CDN
- Google Analytics · Analytics
- HTTP/3 · Miscellaneous
- Mediavine · Advertising
- MySQL · Databases
- PHP · Programming languages
- Super Page Cache · Caching, WordPress plugins
- WordPress · CMS, Blogs
- jQuery · JavaScript libraries
Cloudflare is filed under CDN.
Google Analytics is filed under Analytics.
HTTP/3 is filed under Miscellaneous.
Mediavine is filed under Advertising.
MySQL is filed under Databases.
PHP is filed under Programming languages.
Super Page Cache is filed under Caching, WordPress plugins.
WordPress is filed under CMS, Blogs.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 55 ms. The target title is 51 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 55 ms |
| Title length | 51 yes |
| Quoted title | "ConnectUS – A Christian Blog for Your Walk of Faith" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | yes |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en-US |
| Links | 103 |
| Images | 30 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for connectusfund.org is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | yes |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 5 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
First checked on 30 October 2026; changes will appear here.
Questions
Is connectusfund.org safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts connectusfund.org?
connectusfund.org is placed in Toronto, Canada.
When does connectusfund.org expire?
connectusfund.org expires on 21 April 2028 according to https://rdap.publicinterestregistry.org/rdap/domain/connectusfund.org.
Who owns connectusfund.org?
The registry did not return a person or a company for connectusfund.org. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.publicinterestregistry.org/rdap/domain/connectusfund.org at 2026-10-30T15:01:49Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:01:49Z
- TLS source tls:443 at 2026-10-30T15:01:49Z
- HTTP source https://connectusfund.org/ at 2026-10-30T15:01:49Z
- Tech source wappalyzergo at 2026-10-30T15:01:49Z
- Geo source db-ip at 2026-10-30T15:01:49Z
- Safety source family DNS and local lists at 2026-10-30T15:01:49Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.