fightfuckfeed.me
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 88 days left5 years old
70
fightfuckfeed.me was registered on 28 Jan 2021 via Domain.com - Network Solutions, LLC and the registry expiry is 28 Jan 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/fightfuckfeed.me.
fightfuckfeed.me publishes 4 nameservers. DNSSEC is not signed.
fightfuckfeed.me has 2 IPv4 addresses (35.157.26.135, 63.176.8.218). The geolocation database places 35.157.26.135 in Frankfurt am Main, Germany.
The TLS certificate from YE1 is valid and has 88 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Google Analytics, HSTS and Netlify. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for fightfuckfeed.me in the checks that ran.
Domain · RDAP/WHOIS
fightfuckfeed.me was registered on 28 Jan 2021 via Domain.com - Network Solutions, LLC. The registry returned 1 status value and 4 nameservers from https://rdap.identitydigital.services/rdap/domain/fightfuckfeed.me.
| Registered | since 28 Jan 2021 |
|---|---|
| Created | 28 January 2021 |
| Updated | 12 August 2026 |
| Expires | 28 January 2027 |
| Registrar | Domain.com - Network Solutions, LLC |
| Status | client transfer prohibited |
| Nameservers | dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net |
| DNSSEC | no |
| Source | https://rdap.identitydigital.services/rdap/domain/fightfuckfeed.me |
fightfuckfeed.me 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.p06.nsone.net is published for fightfuckfeed.me in the registration record from https://rdap.identitydigital.services/rdap/domain/fightfuckfeed.me.
Nameserver dns2.p06.nsone.net is published for fightfuckfeed.me in the registration record from https://rdap.identitydigital.services/rdap/domain/fightfuckfeed.me.
Nameserver dns3.p06.nsone.net is published for fightfuckfeed.me in the registration record from https://rdap.identitydigital.services/rdap/domain/fightfuckfeed.me.
Nameserver dns4.p06.nsone.net is published for fightfuckfeed.me in the registration record from https://rdap.identitydigital.services/rdap/domain/fightfuckfeed.me.
DNS
fightfuckfeed.me has 2 address records, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 35.157.26.135, 63.176.8.218 |
|---|---|
| AAAA | — |
| NS | dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 35.157.26.135 answers for fightfuckfeed.me at resolver 1.1.1.1:53.
IPv4 address 63.176.8.218 answers for fightfuckfeed.me at resolver 1.1.1.1:53.
Hosting and geo
fightfuckfeed.me is placed in Frankfurt am Main, Germany by the local geolocation database (db-ip).
| Address | 35.157.26.135 |
|---|---|
| Country | Germany |
| City | Frankfurt am Main |
| Source | db-ip |
SSL/TLS
The certificate for fightfuckfeed.me is valid, with 88 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | fightfuckfeed.me |
| Valid from | 30 October 2026 |
| Valid until | 28 January 2027 |
| Days left | 88 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.fightfuckfeed.me, fightfuckfeed.me.
Tech stack
Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.
- Google Analytics · Analytics
- HSTS · Security
- Netlify · PaaS, CDN
Google Analytics is filed under Analytics.
HSTS is filed under Security.
Netlify is filed under PaaS, CDN.
On-page checks
The homepage returned HTTP 200 in 379 ms. The target title is 16 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 379 ms |
| Title length | 16 yes |
| Quoted title | "FightFuckFeed.me" |
| Meta description | "Play the ultimate procedurally generated vore-focused sandbox text adventure with jungles to explore and castles to conquer. Get more powerful by eating cute monstergirls, and gain unique allies by bonking them!" yes |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en-US |
| Links | 0 |
| 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.
Security
Family DNS for fightfuckfeed.me 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.
Score breakdown
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.
Change history
- October 2026: rdap created changed from 2021-01-28T05:28:08Z to 2021-01-28T05:28:08.066Z.
- October 2026: rdap dnssec changed from unknown to no.
- October 2026: rdap expires changed from 2027-01-28T05:28:08Z to 2027-01-28T05:28:08.066Z.
- October 2026: rdap statuses changed from clienttransferprohibited to client transfer prohibited.
- October 2026: rdap updated changed from 2026-08-12T09:07:28Z to 2026-08-12T09:07:28.685Z.
- October 2026: geo city changed from empty to Frankfurt am Main.
- October 2026: geo country changed from empty to Germany.
Questions
Is fightfuckfeed.me safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts fightfuckfeed.me?
fightfuckfeed.me is placed in Frankfurt am Main, Germany.
When does fightfuckfeed.me expire?
fightfuckfeed.me expires on 28 January 2027 according to https://rdap.identitydigital.services/rdap/domain/fightfuckfeed.me.
Who owns fightfuckfeed.me?
The registry did not return a person or a company for fightfuckfeed.me. RDAP often redacts the registrant. The registrar on file is Domain.com - Network Solutions, LLC.
Sources
- RDAP source https://rdap.identitydigital.services/rdap/domain/fightfuckfeed.me at 2026-10-30T14:43:56Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:43:56Z
- TLS source tls:443 at 2026-10-30T14:43:56Z
- HTTP source https://fightfuckfeed.me/ at 2026-10-30T14:43:56Z
- Tech source wappalyzergo at 2026-10-30T14:43:56Z
- Geo source db-ip at 2026-10-30T14:43:56Z
- Safety source family DNS and local lists at 2026-10-30T14:43:56Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
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.
How to read this report
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.