crazyforfeet.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
60
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
60
crazyforfeet.com was registered on 23 Apr 2008 via 1API GmbH and the registry expiry is 23 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/crazyforfeet.com.
crazyforfeet.com publishes 4 nameservers. DNSSEC is not signed.
crazyforfeet.com has 1 IPv4 address (208.74.149.237). The geolocation database places 208.74.149.237 in Farmington Hills, United States.
The TLS certificate from YR1 is valid and has 32 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.
crazyforfeet.com was registered on 23 Apr 2008 via 1API GmbH. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/com/v1/domain/crazyforfeet.com.
| Registered | since 23 Apr 2008 |
|---|---|
| Created | 23 April 2008 |
| Updated | 10 March 2026 |
| Expires | 23 April 2027 |
| Registrar | 1API GmbH |
| Status | client transfer prohibited |
| Nameservers | dnsa.mojohost.com, dnsb.mojohost.com, dnsc.mojohost.com, dnsd.mojohost.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/crazyforfeet.com |
crazyforfeet.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 dnsa.mojohost.com is published for crazyforfeet.com in the registration record from https://rdap.verisign.com/com/v1/domain/crazyforfeet.com.
Nameserver dnsb.mojohost.com is published for crazyforfeet.com in the registration record from https://rdap.verisign.com/com/v1/domain/crazyforfeet.com.
Nameserver dnsc.mojohost.com is published for crazyforfeet.com in the registration record from https://rdap.verisign.com/com/v1/domain/crazyforfeet.com.
Nameserver dnsd.mojohost.com is published for crazyforfeet.com in the registration record from https://rdap.verisign.com/com/v1/domain/crazyforfeet.com.
crazyforfeet.com has 1 address record, 1 mail exchanger and 4 nameservers, measured at 1.1.1.1:53.
| A | 208.74.149.237 |
|---|---|
| AAAA | — |
| NS | dnsa.mojohost.com, dnsb.mojohost.com, dnsc.mojohost.com, dnsd.mojohost.com |
| MX | mail.crazyforfeet.com (10) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at crazyforfeet.com is "v=spf1 a mx ip4:208.74.149.237 include:amazonses.com ~all".
The DMARC text record at _dmarc.crazyforfeet.com is "v=DMARC1; p=quarantine;".
IPv4 address 208.74.149.237 answers for crazyforfeet.com at resolver 1.1.1.1:53.
Mail exchanger mail.crazyforfeet.com has preference 10.
crazyforfeet.com is placed in Farmington Hills, United States by the local geolocation database (db-ip).
| Address | 208.74.149.237 |
|---|---|
| Country | United States |
| City | Farmington Hills |
| Source | db-ip |
The certificate for crazyforfeet.com is valid, with 32 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | crazyforfeet.com |
| Valid from | 4 September 2026 |
| Valid until | 3 December 2026 |
| Days left | 32 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: crazyforfeet.com, www.crazyforfeet.com.
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 115 ms. The target title is 54 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 115 ms |
| Title length | 54 yes |
| Quoted title | "Crazy for Feet - FootFetish Pictures and Message Board" |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 2 |
| Images | 0 |
| 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 crazyforfeet.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 crazyforfeet.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 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 crazyforfeet.com. That resolver covers adult and malware names.
crazyforfeet.com is placed in Farmington Hills, United States.
crazyforfeet.com expires on 23 April 2027 according to https://rdap.verisign.com/com/v1/domain/crazyforfeet.com.
The registry did not return a person or a company for crazyforfeet.com. RDAP often redacts the registrant. The registrar on file is 1API GmbH.
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.