Faymas · Practical guide

Do the Three Faymas Domains Agree on One Canonical URL?

No. On 17 November 2026 the three Faymas domains agreed on one redirect and disagreed on the rest. All three send an http request to https with a 301. After that, faymas.in canonicalises to its apex, faymas.net to its www host, and faymas-in.com has no www hostname at all: three A lookups returned 'Non-existent domain' and curl exited 6 with 'Could not resolve host'. We ran 33 URL variants three times each. Every cell repeated identically. Two canonical hosts, three different chains, one shared hop.

Updated November 17, 2026 · Prompt-text analysis

This guide analyses published prompt text. No generation tests were run.

The one hop they all share

Every domain answered an http request with the same move. http://faymas.in/ returned 301 to https://faymas.in/. So did the other two, with their own hostnames. Three for three. Each repeat matched.

The response headers say where that hop comes from. It carries Location: with a capital L, Server: cloudflare, and a CF-RAY. It carries no cf-cache-status. That is an edge rule, applied before the request reaches an application. The edge upgrades the scheme. It does not pick the final host.

That distinction matters. A 301 is a 301. Two 301s in a row can come from two different owners.

Three answers to 'which host is canonical'

Here is the split. The three domains do not share a canonical host, and one of them does not have a choice to make.

DomainCanonical hostWhat the non-canonical host doeswww in DNS
faymas.inapex, no www301 to https://faymas.in/resolves, redirects away
faymas.netwwwapex 301 to https://www.faymas.net/resolves, returns 200
faymas-in.comapex, no wwwnothing; the host does not existNXDOMAIN, 3 of 3

An earlier certificate audit on this site, published on 14 November 2026, recorded those three www facts in a single line: .in sends www to apex, .net sends apex to www, and the www name on -in.com does not resolve. It also noted that a wildcard certificate covering *.faymas-in.com says nothing about whether the hostname exists in DNS. This page takes that one line and measures the whole chain behind it. A certificate covering a name and a redirect from that name are different claims.

So the honest answer to the title is not 'use the apex'. It is not 'use www' either. The rule is per domain.

Two hops, two different senders

Start from the least canonical URL you can write and count the jumps. http://www.faymas.in/ takes two. http://faymas.net/ also takes two. Both end at a 200. The headers in the middle are not the same.

Hophttp://www.faymas.in/http://faymas.net/
1301 Location: https://www.faymas.in/ — capital L, no cache header301 Location: https://faymas.net/ — capital L, no cache header
2301 location: https://faymas.in/ — lowercase l, cf-cache-status: HIT301 Location: https://www.faymas.net/ — capital L, no cache header
3200, via: 1.1 Caddy, x-powered-by: Next.js, cf-cache-status: HIT200, x-powered-by: Next.js

On faymas.in the host-level 301 is emitted by the application side. It uses a lowercase location:, it comes back as a cache HIT, and the 200 behind it carries via: 1.1 Caddy with a Next.js signature. On faymas.net both 301s use the capital-L form with no cache status, so both look like edge rules. Same status code. Same net effect. Different layer of the stack.

Header capitalisation is not part of the HTTP meaning. Field names are case-insensitive. But the exact spelling a server emits is a fingerprint of the code that wrote it. We treat that as supporting evidence for two senders, not as proof of ownership. That is a judgement, and we label it as one.

The third domain never gets a second hop. http://www.faymas-in.com/ produces no response at all. There is no chain to analyse.

How long the chains get

Chain length depends on how badly you write the URL. The cleanest form needs no redirect. The worst form needs two, or fails outright.

Starting URLRedirectsFinal URL
https://faymas.in/0https://faymas.in/
http://faymas.in/1https://faymas.in/
http://www.faymas.in/2https://faymas.in/
https://www.faymas.net/0https://www.faymas.net/
http://faymas.net/2https://www.faymas.net/
http://www.faymas.net/1https://www.faymas.net/
https://faymas-in.com/0https://faymas-in.com/
http://faymas-in.com/1https://faymas-in.com/
http://www.faymas-in.com/none; DNS failsno response, curl exit 6

Notice the asymmetry. On faymas.in the www form costs an extra hop. On faymas.net the apex form costs an extra hop. Each domain charges you for the one it does not want.

Path-level cleanup is where they split widest

Host normalisation is a choice. Path handling is a consequence of whatever application sits behind the edge. Five path variants produced three completely different behaviours.

Variantfaymas.infaymas.netfaymas-in.com
//308 to /, relative Location, via: 1.1 Caddy, cf-cache-status: BYPASS301 to www root, extra slash dropped200, double slash kept
:443/200, port kept in URL301 to www root200, port kept in URL
no trailing slash200, resolves to /301 to www root200, resolves to /
/./200, resolves to /301 to www root200, resolves to /
/InDeX404301 to www/InDeX, then 200301 to apex root, then 200; PHP/8.5.12 + LiteSpeed

The double slash on faymas.in is the only 308 in the whole matrix. It uses a relative location: / instead of an absolute URL, and it comes with via: 1.1 Caddy. A 308 keeps the request method and body. A 301 does not promise that. One character of status code, one very different guarantee.

The mixed-case path is the sharpest split. faymas.in answers 404. faymas.net carries the path across the host redirect and returns 200. faymas-in.com throws the path away entirely, redirects to the bare apex, and returns 200 from a PHP and LiteSpeed stack. Three stacks. Three answers to the same invented path.

We did not test whether those 200 bodies are the same page. We recorded the status codes and the Location headers only.

The query string survives

Both host-level 301s kept a query string intact. https://www.faymas.in/?utm=pp redirected to https://faymas.in/?utm=pp. https://faymas.net/?utm=pp redirected to https://www.faymas.net/?utm=pp. Three repeats each, unchanged.

The third domain had no www host to test. Its apex returned 200 with the query still attached, so there was no redirect to lose it in.

That is a small, useful finding. A canonical host rule that drops the query would break tracking links. Neither of the two redirecting domains does it.

What we did not measure

DNS here was read through one recursive resolver. The answers are non-authoritative and are not a global view. A wildcard-hijacking condition on this host resolves several unrelated names to a single address, so we did not treat any A record as evidence of a site. The NXDOMAIN for www.faymas-in.com is different: three separate A lookups returned 'Non-existent domain' and curl independently failed with exit 6, 'Could not resolve host'. Both agree. That is as far as the DNS claim goes.

We requested root-level URLs and a few invented paths only. We did not measure POST behaviour, 308 method preservation in practice, redirect caching lifetimes, other network vantage points, or what happens behind a login. We did not send any email, open a QUIC connection, or test UDP 443. Certificate contents, mail records and ALPN behaviour were covered in earlier audits on this site and are not repeated here.

No traffic, ranking, revenue, ownership or registration data appears on this page. None was available. Where a result is a tool limit rather than a site property, we say so instead of turning it into a finding.

FAQ

Do all three Faymas domains redirect http to https?

Yes. All three returned a 301 to the https form of the same host on every repeat.

Which Faymas domain uses www as its canonical host?

Only faymas.net. Its apex returned a 301 to https://www.faymas.net/ on all three repeats.

Does www.faymas-in.com exist?

No. Three A lookups returned 'Non-existent domain' and curl exited 6 with 'Could not resolve host'.

Do the redirects keep the query string?

Yes. Both host-level 301s carried ?utm=pp into the Location header unchanged.

Did any domain return a 308?

Yes. faymas.in returned 308 Permanent Redirect with a relative location: / for the double-slash path, the only 308 in the matrix.