nfhconnect.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe25 years old
30
nfhconnect.com was registered on 17 Aug 2001 via MarkMonitor Inc. and the registry expiry is 17 Aug 2028. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/nfhconnect.com.
nfhconnect.com publishes 4 nameservers. DNSSEC is not signed.
No safety warning was recorded for nfhconnect.com in the checks that ran.
Domain · RDAP/WHOIS
nfhconnect.com was registered on 17 Aug 2001 via MarkMonitor Inc.. The registry returned 3 status values and 4 nameservers from https://rdap.verisign.com/com/v1/domain/nfhconnect.com.
| Registered | since 17 Aug 2001 |
|---|---|
| Created | 17 August 2001 |
| Updated | 16 July 2026 |
| Expires | 17 August 2028 |
| Registrar | MarkMonitor Inc. |
| Status | client delete prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone, ha4.markmonitor.zone |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/nfhconnect.com |
nfhconnect.com 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.
nfhconnect.com 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.
nfhconnect.com 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 ha1.markmonitor.zone is published for nfhconnect.com in the registration record from https://rdap.verisign.com/com/v1/domain/nfhconnect.com.
Nameserver ha2.markmonitor.zone is published for nfhconnect.com in the registration record from https://rdap.verisign.com/com/v1/domain/nfhconnect.com.
Nameserver ha3.markmonitor.zone is published for nfhconnect.com in the registration record from https://rdap.verisign.com/com/v1/domain/nfhconnect.com.
Nameserver ha4.markmonitor.zone is published for nfhconnect.com in the registration record from https://rdap.verisign.com/com/v1/domain/nfhconnect.com.
DNS
nfhconnect.com has 0 address records, 4 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | — |
|---|---|
| AAAA | — |
| NS | ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone, ha4.markmonitor.zone |
| MX | mx19a.antispameurope.com (10), mx19b.antispameurope.com (20), mx19c.antispameurope.com (30), mx19d.antispameurope.com (40) |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
Mail exchanger mx19a.antispameurope.com has preference 10.
Mail exchanger mx19b.antispameurope.com has preference 20.
Mail exchanger mx19c.antispameurope.com has preference 30.
Mail exchanger mx19d.antispameurope.com has preference 40.
Hosting and geo
Geolocation for nfhconnect.com is not available. No local city or ASN database is installed, so this report does not guess a country.
| Geolocation | not available |
|---|---|
| Source | maxmind |
SSL/TLS
No TLS certificate was read for nfhconnect.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp: lookup nfhconnect.com on 46.38.252.230:53: no such host
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://nfhconnect.com/": dial tcp: lookup nfhconnect.com on 46.38.252.230:53: no such host
Security
Family DNS for nfhconnect.com 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 | no |
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 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 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 0 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 nfhconnect.com 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 nfhconnect.com?
The host network is not available without a local geolocation database.
When does nfhconnect.com expire?
nfhconnect.com expires on 17 August 2028 according to https://rdap.verisign.com/com/v1/domain/nfhconnect.com.
Who owns nfhconnect.com?
The registry did not return a person or a company for nfhconnect.com. RDAP often redacts the registrant. The registrar on file is MarkMonitor Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/nfhconnect.com at 2026-10-30T14:06:24Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:06:24Z
- TLS source tls:443 at 2026-10-30T14:06:24Z
- HTTP source https://nfhconnect.com/ at 2026-10-30T14:06:24Z
- Tech source not available at 2026-10-30T14:06:24Z
- Geo source db-ip at 2026-10-30T14:06:24Z
- Safety source family DNS and local lists at 2026-10-30T14:06:24Z
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.