nifty.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
60
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
60
nifty.org was registered on 21 May 1997 via Network Solutions, LLC and the registry expiry is 22 May 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/nifty.org.
nifty.org publishes 4 nameservers. DNSSEC is not signed.
nifty.org has 1 IPv4 address (67.205.61.97). The geolocation database places 67.205.61.97 in Ashburn, United States.
The TLS certificate from YR2 is valid and has 85 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Apache HTTP Server. The fingerprints ran on the homepage that was already downloaded.
nifty.org was registered on 21 May 1997 via Network Solutions, LLC. The registry returned 1 status value and 4 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/nifty.org.
| Registered | since 21 May 1997 |
|---|---|
| Created | 21 May 1997 |
| Updated | 12 August 2026 |
| Expires | 22 May 2027 |
| Registrar | Network Solutions, LLC |
| Status | client transfer prohibited |
| Nameservers | ns-1244.awsdns-27.org, ns-1675.awsdns-17.co.uk, ns-201.awsdns-25.com, ns-785.awsdns-34.net |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/nifty.org |
nifty.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 ns-1244.awsdns-27.org is published for nifty.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/nifty.org.
Nameserver ns-1675.awsdns-17.co.uk is published for nifty.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/nifty.org.
Nameserver ns-201.awsdns-25.com is published for nifty.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/nifty.org.
Nameserver ns-785.awsdns-34.net is published for nifty.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/nifty.org.
nifty.org has 1 address record, 2 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 67.205.61.97 |
|---|---|
| AAAA | — |
| NS | ns-1244.awsdns-27.org, ns-1675.awsdns-17.co.uk, ns-201.awsdns-25.com, ns-785.awsdns-34.net |
| MX | mx1.emailsrvr.com (10), mx2.emailsrvr.com (20) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at nifty.org is "v=spf1 include:mxsspf.sendpulse.com include:emailsrvr.com ~all".
The DMARC text record at _dmarc.nifty.org is "v=DMARC1; p=reject".
IPv4 address 67.205.61.97 answers for nifty.org at resolver 1.1.1.1:53.
Mail exchanger mx1.emailsrvr.com has preference 10.
Mail exchanger mx2.emailsrvr.com has preference 20.
nifty.org is placed in Ashburn, United States by the local geolocation database (db-ip).
| Address | 67.205.61.97 |
|---|---|
| Country | United States |
| City | Ashburn |
| Source | db-ip |
The certificate for nifty.org is valid, with 85 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | nifty.org |
| Valid from | 26 October 2026 |
| Valid until | 24 January 2027 |
| Days left | 85 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: nifty.org, www.nifty.org.
Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.
Apache HTTP Server is filed under Web servers.
The homepage returned HTTP 200 in 0 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 0 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| Images | 0 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for nifty.org is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for nifty.org. That resolver covers adult and malware names.
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 10 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 0 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.
Cloudflare family DNS returned a block for nifty.org. That resolver covers adult and malware names.
nifty.org is placed in Ashburn, United States.
nifty.org expires on 22 May 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/nifty.org.
The registry did not return a person or a company for nifty.org. RDAP often redacts the registrant. The registrar on file is Network Solutions, LLC.
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.