nyfco.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
70
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
70
nyfco.org was registered on 7 Feb 2005 via NameCheap, Inc. and the registry expiry is 7 Feb 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/nyfco.org.
nyfco.org publishes 2 nameservers. DNSSEC is not signed.
nyfco.org has 2 IPv4 addresses (188.114.96.3, 188.114.97.3) and 2 IPv6 addresses (2a06:98c1:3120::4, 2a06:98c1:3121::4). The geolocation database places 188.114.96.3 in Toronto, Canada.
The TLS certificate from YE2 is valid and has 48 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named AMP, Cloudflare, Cloudflare Browser Insights, HSTS and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for nyfco.org in the checks that ran.
nyfco.org was registered on 7 Feb 2005 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/nyfco.org.
| Registered | since 7 Feb 2005 |
|---|---|
| Created | 7 February 2005 |
| Updated | 12 August 2026 |
| Expires | 7 February 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | jeff.ns.cloudflare.com, wally.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/nyfco.org |
nyfco.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.
Nameserver jeff.ns.cloudflare.com is published for nyfco.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/nyfco.org.
Nameserver wally.ns.cloudflare.com is published for nyfco.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/nyfco.org.
nyfco.org has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.3, 188.114.97.3 |
|---|---|
| AAAA | 2a06:98c1:3120::4, 2a06:98c1:3121::4 |
| NS | jeff.ns.cloudflare.com, wally.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 188.114.96.3 answers for nyfco.org at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for nyfco.org at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::4 answers for nyfco.org at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::4 answers for nyfco.org at resolver 1.1.1.1:53.
nyfco.org is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.3 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for nyfco.org is valid, with 48 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | nyfco.org |
| Valid from | 20 September 2026 |
| Valid until | 19 December 2026 |
| Days left | 48 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.nyfco.org, nyfco.org.
Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.
AMP is filed under JavaScript frameworks.
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
The homepage returned HTTP 200 in 31 ms. The target title is 78 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 31 ms |
| Title length | 78 no |
| Quoted title | "IKAN138: Bergabung Dalam Program Kemitraan Dengan Reward Berdasarkan Aktivitas" |
| Meta description | "IKAN138 menyediakan program kemitraan dengan sistem reward yang disesuaikan berdasarkan aktivitas dan kontribusi partner. Program ini dirancang dengan alur yang jelas sehingga calon partner dapat memahami mekanisme, ketentuan, serta berbagai informasi terkait kemitraan secara lebih mudah." yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | index,follow |
| Canonical | https://superlinkjp.com/ |
| Language | — |
| Links | 41 |
| Images | 36 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for nyfco.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 | yes |
| 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.
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.
First checked on 30 October 2026; changes will appear here.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
nyfco.org is placed in Toronto, Canada.
nyfco.org expires on 7 February 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/nyfco.org.
The registry did not return a person or a company for nyfco.org. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
No other indexable reports share this TLD, host, or registrar yet.
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.
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.