TeckJB
Article

ferizy.com — domain analysis

ferizy.com describes itself as "Pesan tiket kapal ferry mudah, aman dan cepat. Ferizy Naik Ferry, Easy!". It was registered in 2020, served from West Jakarta, Indonesia. It has a valid HTTPS certificate, 4 of 6 common security headers, 1 tracking script.

200HTTP status
4331msResponse time
328Words on the homepage
4/6Security headers set

What is ferizy.com about?

The words appearing most often on the homepage, excluding common filler, are
a rough indication of subject matter rather than a description of the business:

  • check ×9
  • pelabuhan ×8
  • kendaraan ×7
  • masuk ×6
  • promo ×5
  • jadwal ×5
  • jasa ×5
  • lihat ×5
  • kami ×5
  • berita ×4

Does ferizy.com publish the usual trust pages?

None of about, contact, privacy or terms could be found at their usual addresses.
That is common for small or single-purpose sites, and it is also what a disposable
site looks like, so it is worth noting rather than concluding from.

These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.

How does ferizy.com compare with other domains analysed here?

Measured against the 73 domains in this index. This is a
small, self-selected sample — the domains people happened to look up — not a
representative sample of the web.

Response time Faster than 5% of them
(median 516ms)
Security headers More than 75% of them
Domain age Older than 40% of them

Related domains in this index

Analysed domains built on a similar stack:

When was ferizy.com registered?

ferizy.com was registered on 7 February 2020, which makes it about 6 years old.

The registrar of record is Web Commerce Communications Limited dba WebNic.cc.

Registration runs until 7 February 2027.

The domain carries 3 registry locks, which blocks unauthorised transfer or deletion.

Registered 7 February 2020
Expires 7 February 2027
Registrar Web Commerce Communications Limited dba WebNic.cc
Registry status client delete prohibited, client transfer prohibited, client update prohibited

Where is ferizy.com hosted?

The first address resolves to infrastructure in West Jakarta, Indonesia.

The network is operated by PT. Telekomunikasi Indonesia (AS7713 PT Telekomunikasi Indonesia).

Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.

What is ferizy.com running on?

ferizy.com exposes 3 identifiable technologies: Bootstrap, jQuery, Google Analytics.

Visitor tracking is present (Google Analytics), so this homepage is not cookie-free.

  • Bootstrap
  • jQuery
  • Google Analytics

How does the homepage respond?

The server answered with HTTP 200 over
HTTPS.

At 4331ms to first byte this response is very slow for a homepage measured from a single European location.

The HTML weighs 97KB, which is ordinary for a homepage.

No compression is applied to the HTML. Enabling gzip or brotli usually cuts transfer size by around two thirds at no cost to the server.

Server header nginx
Compression none
Page size 99,234 bytes
Declared language en
Mobile viewport declared

What does the homepage say about itself?

The title is 26 characters, inside the range that displays without truncation.

A meta description of 71 characters is present.

No H1 heading was found, so the page offers no single top-level statement of what it is.

6 of 23 images carry no alt attribute, which leaves them unreadable to screen readers and uninterpretable to image search.

Title Ferizy – Naik Ferry, Easy! (26 chars)
Meta description Pesan tiket kapal ferry mudah, aman dan cepat. Ferizy Naik Ferry, Easy! (71 chars)
H1 — none — (0 on the page)
Canonical not set
Open Graph title not set
Headings / images 1 H2s, 23 images (6 without alt text)

Is ferizy.com served over a valid certificate?

The HTTPS certificate is issued by DigiCert Inc and is
valid until 2027-01-10, which is 97 days from the date of this check. It covers
2 hostnames.

  • ferizy.com
  • www.ferizy.com

The certificate has 97 days left to run.

It covers 2 hostnames, so it was issued for this site specifically.

Which security headers does it set?

4 of 6 are set (HSTS, X-Content-Type-Options, X-Frame-Options, Permissions-Policy). Absent: Content Security Policy, Referrer-Policy.

With no Content Security Policy, any script that reaches the page — including one injected through a compromised third-party dependency — runs with full access to it.

Header Set Value
HSTS yes max-age=31536000; includeSubDomains
Content Security Policy no —
X-Content-Type-Options yes nosniff
X-Frame-Options yes SAMEORIGIN
Referrer-Policy no —
Permissions-Policy yes geolocation=(self)

How is DNS configured for ferizy.com?

IP addresses 36.66.3.22
Reverse DNS 36.66.3.22
Name servers ns3.ferizy.com, ns1.ferizy.com, ns2.ferizy.com
Mail (MX) smtp.google.com (pri 1)
SPF v=spf1 a mx a:spf.ferizy.com -all
TXT records 3

ferizy.com resolves to a single address, so there is no DNS-level redundancy.

Mail is handled by 1 exchanger.

An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.

Reverse DNS resolves to 36.66.3.22, which usually names the hosting provider.

Who runs DNS and mail for ferizy.com?

Mail is handled by Google Workspace.

No AAAA records are published, so the site is reachable over IPv4 only.

What else is worth noting about ferizy.com?

41 of 42 externally hosted scripts carry no subresource integrity hash. If one of those hosts were compromised, the replacement script would run with full access to the page.

6 email addresses appear in the homepage markup, where address-harvesting crawlers will find them.

Can ferizy.com be spoofed in email?

DMARC is published with p=none, which monitors but does not act. Forged mail is still delivered; the owner just gets reports about it.

No CAA records are published, so any certificate authority may issue a certificate for this domain.

The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.

What does robots.txt allow?

No robots.txt was served. Crawlers treat a missing file as permission to crawl
everything, so this is an open crawl policy by default rather than a blocked one.

What structured data does the homepage publish?

No JSON-LD or microdata was found on the homepage.

What does ferizy.com load from third parties?

The homepage pulls resources from 7 third-party hosts (browser.sentry-cdn.com, cdnjs.cloudflare.com, fonts.googleapis.com, fonts.gstatic.com, googletagmanager.com, gstatic.com). Each one sees the visitor IP and user agent on every page load.

3 cookies are set before any interaction (route, ferizy, _got). 2 lack the Secure flag.

The page links or refers to X/Twitter, Facebook, Instagram, YouTube.

Cookie Secure HttpOnly SameSite
route yes yes none/unset
ferizy no yes none/unset
_got no no none/unset

Does ferizy.com settle on one address?

Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.

The www hostname does not respond at all, so anyone typing www.ferizy.com reaches nothing.

How easily can ferizy.com be crawled?

No readable sitemap was found, so crawlers have to discover every page by following links.

A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.

What tracking does ferizy.com run?

1 tracking script detected: Google Analytics.

No consent management platform was detected alongside them. Where GDPR or the ePrivacy Directive applies, analytics and advertising scripts generally need consent before they load.

How does ferizy.com look when shared?

No Open Graph or Twitter Card tags are present. Links shared to social platforms will fall back to whatever the platform can scrape, usually just a bare URL.

How are images, fonts and scripts handled?

23 images on the homepage, 4 of them lazy-loaded (17%).

Modern image formats are in use (9 WebP/AVIF references).

Fonts are loaded from Google Fonts, which means every page view also contacts Google. Self-hosting removes that dependency.

The page pulls 25 external stylesheets and 42 external scripts, with 7 carrying defer or async.

Is ferizy.com accessible and current?

The page uses 3 landmark elements and 18 ARIA attributes.

The viewport tag disables pinch-zoom. That fails WCAG 1.4.4 and is a genuine problem for anyone who needs to enlarge text.

There are 27 form inputs but only 21 label elements, so some fields may be unlabelled for screen readers.

No skip-to-content link was found, which keyboard users rely on to bypass navigation.

2 deprecated HTML elements are still in use (center, font, marquee or blink).

Can search engines index ferizy.com?

Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.

No canonical URL is declared, which leaves duplicate addresses of this page to be resolved by the search engine.

The homepage carries 23 internal and 8 external links across 7 outside hosts.

Visible text is only 2.3% of the HTML, which indicates the page is assembled in the browser rather than served as content.

The heading outline skips 3 levels, which breaks the document structure screen readers navigate by.

How is ferizy.com delivered?

The HTML is served with Cache-Control: no-store, no-cache, must-revalidate.

A web app manifest is declared, so the site is installable as a progressive web app.

The TLS certificate also covers 1 subdomain: www.ferizy.com.

  • www.ferizy.com

Frequently asked questions

Does ferizy.com set the usual HTTP security headers?

It sets 4 of 6. The ones not present are: Content Security Policy, Referrer-Policy.

Does ferizy.com allow AI crawlers?

No robots.txt is served, so nothing is disallowed and AI crawlers are free to read the site.

What is ferizy.com built with?

The homepage exposes these fingerprints: Bootstrap, jQuery, Google Analytics. A site behind a CDN or rendered server-side may use more than it reveals.

Where does this data come from?

Every figure was measured by our own server on 5 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.

Is any of this traffic or authority data?

No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.

I own ferizy.com and want this page removed.

Ask through the contact page on this site, from an address at the domain, and the report will be taken down. It only ever shows what the domain already serves publicly.

Analysed 5 October 2026.
Analyse another domain →

Related guides