imageflea.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
imageflea.com was registered on 23 May 2008 via NameCheap, Inc. and the registry expiry is 23 May 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/imageflea.com.
imageflea.com publishes 2 nameservers. DNSSEC is not signed.
imageflea.com has 1 IPv4 address (23.138.140.174). The geolocation database places 23.138.140.174 in New York, United States.
The TLS certificate from YR2 is valid and has 56 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, Google Analytics, Nginx, PHP, Yii and jQuery. The fingerprints ran on the homepage that was already downloaded.
imageflea.com was registered on 23 May 2008 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/imageflea.com.
| Registered | since 23 May 2008 |
|---|---|
| Created | 23 May 2008 |
| Updated | 23 April 2026 |
| Expires | 23 May 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | miles.ns.cloudflare.com, mira.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/imageflea.com |
imageflea.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.
Nameserver miles.ns.cloudflare.com is published for imageflea.com in the registration record from https://rdap.verisign.com/com/v1/domain/imageflea.com.
Nameserver mira.ns.cloudflare.com is published for imageflea.com in the registration record from https://rdap.verisign.com/com/v1/domain/imageflea.com.
imageflea.com has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 23.138.140.174 |
|---|---|
| AAAA | — |
| NS | miles.ns.cloudflare.com, mira.ns.cloudflare.com |
| MX | mx.ufobe.com (10) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at imageflea.com is "v=spf1 a mx a:google.com a:kaktuz.net a:go-015.kaktuz.net ip4:104.250.138.186 include:aspmx.googlemail.com include:_spf.google.com ipv4:173.208.178.30 a:mx.ufobe.com a:pds3.ufobe.c…".
IPv4 address 23.138.140.174 answers for imageflea.com at resolver 1.1.1.1:53.
Mail exchanger mx.ufobe.com has preference 10.
A random label under imageflea.com also resolved, which means wildcard DNS is on.
imageflea.com is placed in New York, United States by the local geolocation database (db-ip).
| Address | 23.138.140.174 |
|---|---|
| Country | United States |
| City | New York |
| Source | db-ip |
The certificate for imageflea.com is valid, with 56 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | imageflea.com |
| Valid from | 28 September 2026 |
| Valid until | 27 December 2026 |
| Days left | 56 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: imageflea.com, www.imageflea.com.
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
Bootstrap is filed under UI frameworks.
Google Analytics is filed under Analytics.
Nginx is filed under Web servers, Reverse proxies.
PHP is filed under Programming languages.
Yii is filed under Web frameworks.
jQuery is filed under JavaScript libraries.
The homepage returned HTTP 200 in 149 ms. The target title is 51 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 149 ms |
| Title length | 51 yes |
| Quoted title | "ImageFlea - pic hosting - Sexy Babes Porn Galleries" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://imageflea.com/s |
| Language | en-US |
| Links | 208 |
| Images | 39 |
| 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 imageflea.com 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 imageflea.com. 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 5 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 imageflea.com. That resolver covers adult and malware names.
imageflea.com is placed in New York, United States.
imageflea.com expires on 23 May 2027 according to https://rdap.verisign.com/com/v1/domain/imageflea.com.
The registry did not return a person or a company for imageflea.com. 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.