fapit.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
50
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
50
fapit.org was registered on 5 Aug 2009 via PDR Ltd. d/b/a PublicDomainRegistry.com and the registry expiry is 5 Aug 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/fapit.org.
fapit.org publishes 4 nameservers. DNSSEC is not signed.
fapit.org has 1 IPv4 address (185.38.185.113). The geolocation database places 185.38.185.113 in Haarlem (Haarlemmerbuurt-Oost), The Netherlands.
The TLS certificate from YE1 is valid and has 61 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Liveinternet, MySQL, Nginx, PHP, Twenty Twenty, Ubuntu and WordPress. The fingerprints ran on the homepage that was already downloaded.
fapit.org was registered on 5 Aug 2009 via PDR Ltd. d/b/a PublicDomainRegistry.com. The registry returned 1 status value and 4 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/fapit.org.
| Registered | since 5 Aug 2009 |
|---|---|
| Created | 5 August 2009 |
| Updated | 12 August 2026 |
| Expires | 5 August 2027 |
| Registrar | PDR Ltd. d/b/a PublicDomainRegistry.com |
| Status | client transfer prohibited |
| Nameservers | dns1.regway.com, dns2.regway.com, dns3.regway.com, dns4.regway.com |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/fapit.org |
fapit.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 dns1.regway.com is published for fapit.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/fapit.org.
Nameserver dns2.regway.com is published for fapit.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/fapit.org.
Nameserver dns3.regway.com is published for fapit.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/fapit.org.
Nameserver dns4.regway.com is published for fapit.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/fapit.org.
fapit.org has 1 address record, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 185.38.185.113 |
|---|---|
| AAAA | — |
| NS | dns1.regway.com, dns2.regway.com, dns3.regway.com, dns4.regway.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 185.38.185.113 answers for fapit.org at resolver 1.1.1.1:53.
fapit.org is placed in Haarlem (Haarlemmerbuurt-Oost), The Netherlands by the local geolocation database (db-ip).
| Address | 185.38.185.113 |
|---|---|
| Country | The Netherlands |
| City | Haarlem (Haarlemmerbuurt-Oost) |
| Source | db-ip |
The certificate for fapit.org is valid, with 61 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | fapit.org |
| Valid from | 2 October 2026 |
| Valid until | 31 December 2026 |
| Days left | 61 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: fapit.org.
Tech detection checked the fetched homepage and named 7 products. Source: wappalyzergo.
Liveinternet is filed under Analytics.
MySQL is filed under Databases.
Nginx is filed under Web servers, Reverse proxies.
PHP is filed under Programming languages.
Twenty Twenty is filed under WordPress themes.
Ubuntu is filed under Operating systems.
WordPress is filed under CMS, Blogs.
The homepage returned HTTP 200 in 347 ms. The target title is 24 characters and the page has 2 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 347 ms |
| Title length | 24 yes |
| Quoted title | "18+ Rare and leaked porn" |
| Meta description | none no |
| H1 count | 2 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | max-image-preview:large |
| Canonical | — |
| Language | en-US |
| Links | 394 |
| Images | 31 |
| 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 fapit.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 fapit.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 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 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 fapit.org. That resolver covers adult and malware names.
fapit.org is placed in Haarlem (Haarlemmerbuurt-Oost), The Netherlands.
fapit.org expires on 5 August 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/fapit.org.
The registry did not return a person or a company for fapit.org. RDAP often redacts the registrant. The registrar on file is PDR Ltd. d/b/a PublicDomainRegistry.com.
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.