One host, and it is only a hostname. Across 27 pages on faymas.in, faymas.net, faymas-in.com and faymas.com.in we found 20 distinct third-party hosts declared in the server HTML. Nineteen of them appear on exactly one domain. The single host that shows up on all four is googletagmanager.com — and even there, the four domains use four different measurement IDs (GTM-PJTJFKBQ, GTM-5HD7ZXT7, GT-NNZ3H2NQ, G-364NQH61SV). Measured 2026-10-18.
This guide analyses published prompt text. No generation tests were run.
What we measured, and what we did not
We crawled 27 pages: 10 on faymas.in (home, /blog, 8 prompt pages drawn at random from the 19,133 /prompt/ URLs in its sitemap), 9 on www.faymas.net (home, /about and 7 others from its 41-page sitemap), 4 on faymas-in.com (home plus all 3 WordPress posts) and 4 on faymas.com.in (home plus all 4 WordPress pages). Both WordPress domains were enumerated through their WP REST API, not guessed.
From each page we pulled every src and href on script, link, img, iframe, source, video and anchor tags, kept the ones pointing at a host other than the page's own domain, and normalised www. away. That gives a list of third-party hosts declared in the HTML.
Two limits. We never request those hosts — this environment's DNS resolves unrelated domains to the same address, so we count declarations, not successful loads. And we read server HTML only: anything injected by JavaScript after render is invisible here. Both limits cut the same way, toward undercounting.
Twenty hosts, nineteen of them private
The four domains declare 20 distinct third-party hosts between them. Exactly one appears on more than a single domain, and it appears on all four.
| Domain | Pages crawled | Distinct 3rd-party hosts | External refs per page |
|---|---|---|---|
| faymas.in | 10 | 9 | 12–13 |
| www.faymas.net | 9 | 4 | 3–59 |
| faymas-in.com | 4 | 7 | 2 |
| faymas.com.in | 4 | 3 | 1–2 |
Pairwise overlap is close to nil. Shared hosts over union, for all six pairs: 0.067, 0.083, 0.091, 0.100, 0.111 and 0.167. The highest pair is faymas.net with faymas.com.in, and that is one host out of six — googletagmanager.com again.
So the four sites share a vendor, not an account.
Four domains, four measurement IDs
If one operator ran all four, the cheapest thing to reuse is the analytics container. None of them did.
| Domain | Measurement ID | Pages it appears on | Ad hosts |
|---|---|---|---|
| faymas.in | GTM-PJTJFKBQ (container) | 10 of 10 | 4 |
| www.faymas.net | GTM-5HD7ZXT7 (container) | 9 of 9 | 0 |
| faymas-in.com | GT-NNZ3H2NQ (GA4) | 3 of 4 (not the home page) | 0 |
| faymas.com.in | G-364NQH61SV (GA4) | 4 of 4 | 0 |
The two Google Tag Manager containers differ. The two GA4 properties differ. Nothing is shared except the hostname both products happen to be served from.
Only faymas.in carries an ad stack — and it ships no ad code
faymas.in's nine hosts split cleanly: four Ezoic (ezojs.com, g.ezoic.net, go.ezodn.com, ezoicanalytics.com), two Google advertising (pagead2.googlesyndication.com, securepubads.g.doubleclick.net), two consent-management (cmp.gatekeeperconsent.com, the.gatekeeperconsent.com), plus Google Tag Manager. Every one of the ten pages we opened carries the identical nine. That is a hard-coded template head, not page-level plumbing.
Here is the part that surprised us. faymas.in has zero external <script src> tags in its server HTML. Not one. All nine hosts appear only inside six <link> hints on the home page — three preconnect, two dns-prefetch, one more preconnect — pointing at g.ezoic.net, ezojs.com, go.ezodn.com and securepubads.g.doubleclick.net.
A crawler sees a site that announces an ad stack and delivers none of it. The ads arrive later, by JavaScript, in a browser. That is ordinary practice; it also means the monetisation is invisible to anything that does not run JS.
The publisher ID in the page matches one line of its own ads.txt
faymas.in's HTML carries ca-pub-7263552627178707 on all ten pages. Its ads.txt is 847 lines with MANAGERDOMAIN=adpushup.com and 36 google.com, pub- entries — 9 DIRECT and 27 RESELLER. Line 329 reads:
google.com, pub-7263552627178707, DIRECT, f08c47fec0942fa0
The ID that is actually in the page is one of the nine direct ones. That is a small finding with a useful shape: the other 35 publisher IDs are a reseller chain declared on paper, and this one is the account the pages themselves call.
faymas.net loads media, not ads
faymas.net has no advertising host at all. Its four hosts are Google Tag Manager plus three Cloudflare R2 buckets with default development hostnames — pub-0413a9c78ce549c7904a53ab4fc53a9a.r2.dev, pub-ba45bd3ba59f468abbaa7fcd010f5954.r2.dev and pub-c1d54745e9b34241adf3297da6711a87.r2.dev — serving images and video.
The image counts tell you which pages are showcases and which are forms. The home page pulls 21 external images, /prompts/ai-photo-editing-prompts 36, /prompts/faymas-ai-prompts 54 and /prompts/awesome-gpt-image-prompts 54. The four model pages and /about pull zero.
The only link between any two of the four
Across all 27 pages, exactly one anchor points from one of these domains at another. It sits on faymas.com.in's home page: https://faymas.in/, anchor text "Get AI Photo Prompts", carrying rel=" nofollow noopener". The string faymas.in occurs once in that entire page.
That domain also loads avads.live/s/av-onstreamapk.js — a script named after a different product altogether — which is the same mismatch we flagged when its og:site_name came back as something other than Faymas.
The split is by stack, not by owner
Sort the four by what they physically ship and the line falls somewhere unexpected. The two Next.js domains, faymas.in and faymas.net, both ship zero external script tags in server HTML — one uses preconnect hints, the other a GTM noscript iframe. The two WordPress domains, faymas-in.com and faymas.com.in, each write two external <script src> tags straight into the markup.
So the strongest pattern in the runtime data is the framework, not the operator. Whatever connects these four domains, it is not a shared tag container, a shared ad account, or a shared CDN.
What this does and does not prove
It does not prove the four are unrelated businesses. Shared ownership can exist without shared tooling, and we did not check WHOIS, hosting or registrant data for this piece.
What it does show is narrower and, we think, more usable: on the layer where a site has to actually commit — which tag container, which ad account, which storage bucket — these four committed four different ways. The only thing they hold in common is a hostname that anyone can use.
Which leaves the practical version. If you want to know what a site really runs, do not read its source for ad network names; read the network panel after render, because the source may only contain hints. And if you want to know whether a cluster of lookalike domains is one operation, counting pages is the wrong instrument. Count the accounts.
FAQ
Do any of the four Faymas domains share a Google Tag Manager container?
No. faymas.in uses GTM-PJTJFKBQ and faymas.net uses GTM-5HD7ZXT7; the other two domains do not use a container at all, only GA4 properties GT-NNZ3H2NQ and G-364NQH61SV. Measured across 27 pages on 2026-10-18.
How many third-party hosts do the four Faymas domains load in total?
Twenty distinct hosts. Nineteen appear on exactly one domain; only googletagmanager.com appears on all four.
Which Faymas domain actually runs ads?
Only faymas.in, and only in the browser. Its server HTML declares Ezoic and Google advertising hosts but contains zero external script tags, so the ad code is not present for anything that does not execute JavaScript.
Does faymas.net run advertising scripts?
No ad host was found on any of the nine pages crawled. Its four third-party hosts are Google Tag Manager and three Cloudflare R2 buckets that serve images and video.
Is there a link between any two of the four domains?
One. faymas.com.in's home page carries a single anchor to https://faymas.in/ with the text "Get AI Photo Prompts", marked nofollow. No other inter-domain link appeared in the 27 pages crawled.