Almost nothing, and every file that does exist was written by a machine. On 25 October 2026 we requested 20 standard self-declaration files — robots.txt, sitemap.xml, manifest, ads.txt, feed, humans.txt, security.txt, ai.txt, llms.txt and eleven more — from all four faymas domains. Eighty requests, redirects followed. Eighteen returned a real file of the expected type. Forty-four returned 404, and eighteen returned 200 with an HTML page that is not the file you asked for. Cut the list the other way and it gets starker: of the ten files a person would have to sit down and write — humans.txt, security.txt, ai.txt, llms-full.txt, sellers.json, opensearch.xml, browserconfig.xml, mcp.json, app-ads.txt — all forty requests came back empty. Zero out of forty.
This guide analyses published prompt text. No generation tests were run.
What we did
This audit is not about pages. It is about the small files a site puts at its root to state facts about itself: who may crawl it, what it is called, who may sell its ads, where its feed is, who to contact about a security hole. We picked twenty such paths and requested each one from faymas.in, faymas.net, faymas-in.com and faymas.com.in. Twenty times four is eighty GETs, all on 25 October 2026, all following redirects, all with the same user agent.
We classified by content type, not by status code. That distinction is the whole page. faymas-in.com answers seventeen of the twenty requests with 200 OK and a 70,244-byte HTML document that is byte-for-byte its own homepage. faymas.net does the same thing at /feed/ with 99,340 bytes of HTML containing no <title> and no <item>. A 200 here means nothing. A file only counts as real below if the response type is the type that file is supposed to be: text/plain for robots.txt, application/manifest+json for a web app manifest, application/rss+xml for a feed, application/xml for a sitemap, an image type for an icon.
The grid: 80 requests, 18 real files
| File requested | faymas.in | faymas.net | faymas-in.com | faymas.com.in |
|---|---|---|---|---|
/robots.txt | 200 · 407 B | 200 · 149 B | 200 · 117 B | 200 · 117 B |
/sitemap.xml | 200 · 4,346,429 B | 200 · 7,105 B | 200 · html | 404 |
/manifest.webmanifest | 200 · 577 B | 200 · 496 B | 200 · html | 404 |
/site.webmanifest | 404 | 200 · 378 B | 200 · html | 404 |
/manifest.json | 404 | 404 | 200 · html | 404 |
/ads.txt | 200 · 39,282 B | 200 · 59 B | 200 · html | 200 · 7,214 B |
/app-ads.txt | 404 | 404 | 200 · html | 404 |
/feed/ | 404 | 200 · html | 200 · 88,659 B | 200 · 1,004 B |
/humans.txt | 404 | 404 | 200 · html | 404 |
/security.txt | 404 | 404 | 200 · html | 404 |
/.well-known/security.txt | 404 | 404 | 200 · html | 404 |
/ai.txt | 404 | 404 | 200 · html | 404 |
/llms.txt | 200 · 1,907 B | 404 | 200 · html | 404 |
/llms-full.txt | 404 | 404 | 200 · html | 404 |
/mcp.json | 404 | 404 | 200 · html | 404 |
/sellers.json | 404 | 404 | 200 · html | 404 |
/opensearch.xml | 404 | 404 | 200 · html | 404 |
/browserconfig.xml | 404 | 404 | 200 · html | 404 |
/favicon.ico | 200 · 15,086 B | 200 · 15,406 B | 404 | 404 |
/apple-touch-icon.png | 404 | 200 · 11,513 B | 200 · html | 404 |
Real files by domain: faymas.net 7, faymas.in 6, faymas.com.in 3, faymas-in.com 2. The sixty-two misses were not cheap. Across the four domains, the responses that were not the file we asked for added up to 10,726,673 bytes — roughly 10.2 MiB of HTML and redirect paperwork spent saying "no", with faymas.in alone accounting for 5,463,235 bytes of it across 14 misses at about 390 KB each.
The only file all four agree on is the one nobody writes by hand
Robots.txt is present on four of four. It is also the one file on this list that WordPress and Next.js both emit without being asked. Everything else is optional, and the optional files are where the four sites stop resembling each other.
Two of the four robots files are the same file. faymas-in.com and faymas.com.in each serve a 117-byte robots.txt; the only difference between them is line five, the sitemap URL. Both are the stock WordPress pair — Disallow: /wp-admin/ plus Allow: /wp-admin/admin-ajax.php — and both point at a sitemap_index.xml.
One of those two sitemaps exists. faymas-in.com/sitemap_index.xml is 649 bytes of Rank Math output listing three children — post, page and category — with the post sitemap stamped 2026-10-24T08:43:40+00:00. faymas.com.in/sitemap_index.xml is a 404. So does /sitemap.xml there, which redirects to the index and 404s again. Both robots files were written by the same hand; only one of the two sites ever generated the file its robots file promises.
ads.txt: where the four sites differ most
| ads.txt | faymas.in | faymas.net | faymas-in.com | faymas.com.in |
|---|---|---|---|---|
| Where it actually lives | console.manageadstxt.com/49346/ | own domain | — | own domain |
| Size | 39,282 B | 59 B | homepage HTML | 7,214 B |
| Lines | 849 | 1 | — | 166 |
| Ad-system entries | 846 | 1 | — | 118 |
| Distinct systems named | 151 | 1 | — | 49 |
| DIRECT / RESELLER | 249 / 597 | 1 / 0 | — | 47 / 71 |
| Comment lines | 0 | 0 | — | 30 |
Faymas.in's is the telling one. /ads.txt there answers 301 and lands on console.manageadstxt.com/49346/ads.txt — the file that says who is allowed to sell this domain's ad inventory does not live on this domain. It opens with two lines that are not ad systems at all: OWNERDOMAIN=faymas.in and MANAGERDOMAIN=adpushup.com. The rest is 846 entries across 151 systems, three quarters of them RESELLER. That is not a file a site owner typed. It is the output of an ad-operations vendor's console.
Faymas.com.in's is 166 lines, of which 30 are comment — an ASCII-art banner reading "Advergic Exclusive Partner" in block letters, forty characters tall. Under the banner, 118 entries across 49 systems, google.com among them.
Faymas.net's is one line: google.com, pub-7458553257048860, DIRECT, f08c47fec0942fa0. Faymas.in's google line is google.com, pub-6644558441501035, DIRECT, f08c47fec0942fa0 — different publisher ID, identical trailing value. We are reporting that both files carry the same fourth field; we did not verify what it denotes and we are not going to guess.
Faymas-in.com returns 200 for /ads.txt and the bytes are its homepage. If a buyer's crawler trusts the status code, that site looks like it has an authorised-seller file when it has nothing.
The manifest: one site publishes two, and they disagree
Faymas.in declares one app manifest, 577 bytes, linked from its homepage as /manifest.webmanifest. It calls the app "Faymas", describes it as "The Creator Platform for AI Prompts", sets both theme and background to #0A0A0A, and lists three icons — of which two are the same 192×192 file, listed once plain and once as maskable. /site.webmanifest and /manifest.json are 404. One file, one story.
Faymas.net publishes two, and they do not match. /manifest.webmanifest is 496 bytes: name "Faymas AI", a full description ("an all-in-one AI image generator and AI video generator with leading models, practical controls, and reusable creative prompts"), theme and background #070809. /site.webmanifest is 378 bytes: same name, no description, theme and background #17141f. Two brand colours, declared by one domain, in two files that are both live. The homepage links only the first, so the #17141f version is reachable but wired to nothing.
Note what the two descriptions say. One faymas calls itself a creator platform for prompts. The other calls itself an AI image and video generator. Both use the same short name. The WordPress pair publishes no manifest at all — no PWA declaration, no icon set, no theme colour, nothing.
Feeds: four domains, four different kinds of nothing
| Feed | faymas.in | faymas.net | faymas-in.com | faymas.com.in |
|---|---|---|---|---|
/feed/ status | 404 | 200 · text/html | 200 · rss+xml | 200 · rss+xml |
| Size | — | 99,340 B | 88,659 B | 1,004 B |
| Items | — | 0 | 4 | 0 |
| Channel title | — | — | faymas in | Faymas |
| Last build | — | — | 24 Oct 2026 08:43:40 | 5 Oct 2026 23:05:00 |
Faymas-in.com has the only working feed on the list: four items, WordPress 7.1.3, dated 24 October, 3 October, and two from 23 September. It is 88,659 bytes for four posts — about 22 KB each, because each item carries its full body inline (content:encoded runs 14,781, 32,399, 5,023 and 27,413 characters). The newest post's timestamp, 08:43:39, is one second before the post sitemap's lastmod of 08:43:40. Whatever rebuilt that sitemap rebuilt it right after the post went out.
Faymas.com.in has a feed with nothing in it. 1,004 bytes, zero items, channel title "Faymas", one image, and a last build date of 5 October 2026. It also declares sy:updatePeriod hourly and sy:updateFrequency 1 — an empty feed announcing that it refreshes every hour. Titles tell you what a feed is for; this one has a title and no content.
Faymas.net's /feed/ is a 200 with 99,340 bytes of HTML and no feed in it. Faymas.in has no feed anywhere: /feed/, /feed, /feed.xml and /rss.xml all 404. The domain with 21,761 URLs in its sitemap is the one with no way to subscribe to it.
The declared surface does not rank like the sites do
Order the four domains by how big they are and then by how much they declare, and the two lists come out different. By sitemap: faymas.in held 21,761 URLs when we pulled it on 25 October (21,432 on 24 October, so about 329 a day); faymas.net holds 41; faymas-in.com holds three sub-sitemaps; faymas.com.in is a handful of pages. By declared files: faymas.net 7, faymas.in 6, faymas.com.in 3, faymas-in.com 2.
So the site with 41 URLs publishes more root-level declaration files than the site with 21,761, and the smallest domain on the list carries an ads.txt with 118 authorised-seller entries while the biggest carries no feed at all. Size and self-disclosure are not correlated here, which is what you would expect if these files were never decisions. A file that a framework or a plugin emits lands on the site whether the site is 21,761 pages or four. A file that requires someone to write a sentence does not land on any of them.
The consequence is practical. If you want to know who runs one of these sites, the file layer will not tell you: no humans.txt, no security.txt, no contact channel beyond a contact page. The only attribution anywhere in eighty requests is vendor-shaped — MANAGERDOMAIN=adpushup.com on one domain, an "Advergic Exclusive Partner" banner on another, and one self-description in a manifest. If you want to report a vulnerability, none of the four publishes a security.txt at either location we tried. If you are an agent looking for a machine contract, faymas.in is still the only domain with an llms.txt, as we found on 24 October.
What we did not measure
Twenty paths is a sample, not an exhaustive sweep; there are other declaration files we did not request. We ran no JavaScript, so anything emitted at runtime is invisible to us. Ad-system entries were counted by matching lines that begin with a domain name followed by a comma; we did not verify any entry against the network it names, and we do not know which of the 846 entries are currently active. Faymas.in's ads.txt was read from its redirect target, not from faymas.in itself. The 70,244-byte body that faymas-in.com returns for seventeen of twenty requests is the homepage under our user agent; a different client may be served something else. We contacted nobody, and we consulted no traffic, ranking or revenue service — every number on this page comes from the eighty responses we saved.
FAQ
Do any of the faymas sites publish a humans.txt or security.txt?
No. Across all four domains we requested humans.txt, security.txt and .well-known/security.txt — twelve requests — and none returned a real file. Nine were 404 and three were HTML pages that are not the file: faymas-in.com's homepage for all three, plus a 7,767-byte HTML response from faymas.net for the .well-known path.
Which faymas domain publishes the most root declaration files?
faymas.net, with seven of twenty: robots.txt, sitemap.xml, two manifests, ads.txt, favicon.ico and apple-touch-icon.png. faymas.in has six, faymas.com.in three, faymas-in.com two.
Why does faymas.in's ads.txt live on another domain?
Because /ads.txt there answers 301 and redirects to console.manageadstxt.com/49346/ads.txt. The file itself names MANAGERDOMAIN=adpushup.com, so it is maintained by an ad-operations vendor rather than served by the site.
Does faymas.com.in have a working sitemap?
No. Its robots.txt declares https://faymas.com.in/sitemap_index.xml and both that path and /sitemap.xml return 404. Its WordPress twin faymas-in.com declares the same file and does serve it.
Which faymas site has a usable RSS feed?
Only faymas-in.com, with four items and a last build date of 24 October 2026. faymas.com.in returns a valid feed with zero items, faymas.net returns 200 with HTML and no items, and faymas.in has no feed at all.