Website profiles · Technology insights · Alternatives

pwasforfirefox.filips.si

A tool to install, manage and use Progressive Web Apps (PWAs) in Mozilla Firefox

No paid content found
Visit website
Profile views 9 Outbound visits 2 Normal
PWAsForFirefox Full homepage screenshot

At a glance

Category
Software & Apps
Language
English
Paid-content signal
No paid content foundObserved
Registered
2016
Hosting
CloudflareInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is PWAsForFirefox?

PWAsForFirefox is a tool that lets you install, manage, and run Progressive Web Apps in Mozilla Firefox. Firefox supports many PWA-related web APIs but does not offer a built-in way to install a site as a standalone app; this project fills that gap by creating a modified Firefox runtime so websites can run in their own window, with their own start menu entry and taskbar icon, and without tabs or an address bar. It provides both a command-line tool and a browser extension for installing and managing apps and their profiles.

How it works in practice

You install the browser extension, follow the in-browser setup instructions, and the extension handles creating and patching the native runtime and profile. Installed PWAs live in an isolated Firefox installation and profile, and you can install essentially any website as an app. Because the runtime is Firefox-based, installed apps retain support for Firefox extensions and built-in browser features.

Who it suits

  • Firefox users who want app-like web tools without switching to another browser for that purpose.
  • People who prefer separate windows and profiles for work, communication, or media sites instead of a crowded tab bar.
  • Users comfortable with an extension plus a native component rather than a purely click-to-install browser feature.

Trade-offs to weigh

The setup is more involved than installing a PWA in a browser that supports it natively, since it relies on a modified runtime and profile that must be installed and kept patched. That isolation is also the main benefit: apps stay separate from your main Firefox session. If you want the simplest possible path, a browser with native PWA installation will be easier; if you want to stay in Firefox, this is the practical route.

For a concrete example, someone who uses a web-based chat or project tool all day could install it as a PWA so it opens in its own window with a taskbar icon, while keeping their normal browsing tabs untouched. Start by checking the project's installation and user guide pages, then install the extension and set up one app to see whether the workflow fits.

How do I install PWAsForFirefox on my system?

PWAsForFirefox installs in two parts: a native runtime/program on your computer, and a Firefox browser extension that drives it. The website's installation page is the authoritative sequence; the short version is below.

Basic installation flow

  1. Install the native program. Use the project's installer for your platform (Linux packages, Windows installer, or macOS package, depending on what the installation page lists). This creates an isolated Firefox installation and profile(s) used specifically for PWAs.
  2. Install the browser extension. Add the PWAsForFirefox extension to your main Firefox browser, then follow the in-browser setup instructions it presents. The extension is what lets you install, manage, and run PWAs and their profiles without touching the command line.
  3. Install your first PWA. Open the site you want in Firefox, trigger installation from the extension (or the command-line tool), and it appears as a standalone window with its own start/app menu entry and taskbar icon.

Which method to choose

Situation Recommended approach
You want a graphical, click-through setup Browser extension plus in-browser instructions
You prefer scripting or headless management Command-line tool
You only want to try one site quickly Extension, one PWA, no extra profiles

Practical notes

  • The project uses a custom modified Firefox runtime, so your normal Firefox profile stays separate from the PWA profiles. This is the main reason installed PWAs feel app-like: no tabs, no address bar, own window.
  • Automatic installation and patching are user-triggered, so expect to approve updates rather than have them happen silently.
  • All Firefox add-ons and built-in features remain available inside installed PWAs, which matters if you rely on extensions for password managers or content blocking.
  • If setup fails, the project's FAQ and help section are the intended first stop; the repository README has the fuller technical detail.

A sensible next step: read the installation page once end to end before running anything, then install the extension first so it can guide the native program setup. If you are on Linux and prefer package managers, check whether your distribution's repositories or the project's DEB/RPM packages are the smoother path for your system.

How do I install a website as a Progressive Web App in Firefox using this tool?

PWAsForFirefox adds standalone app installation to Firefox, which does not support it natively. You install a site as a PWA in two stages: first set up the tool itself, then install the site from Firefox.

Set up the tool

  1. Install the modified Firefox runtime and the companion browser extension. The project provides a command-line tool for installing, managing and running PWAs, plus an extension for in-browser control.
  2. Follow the in-browser installation instructions on the project's installation page. The extension is what connects the main Firefox browser to the native programs and to the isolated Firefox installation and profile(s) where PWAs are stored.
  3. If setup fails, the help section and FAQ page are the intended first stop.

Install a website as a PWA

  1. Open the site in your main Firefox browser with the extension active.
  2. Use the extension to install that site as a PWA. The project states that all websites can be installed, not only ones that ship a web app manifest.
  3. Launch the PWA from its own start/app menu entry or taskbar icon. It opens in its own window with no tabs and no address bar, which is the main reason to use it over a normal Firefox tab.

What you get, and the trade-offs

Aspect What this tool does Practical effect
Runtime Uses a separate modified Firefox installation and profile(s) PWAs are isolated from your everyday browsing profile
Window Own window, no tabs or address bar Closer to a native app; less convenient for heavy tab use
Site support Any website can be installed Useful for internal tools and sites that never added PWA support
Extensions Firefox add-ons and built-in features are supported Your usual extensions can work inside the PWA
Updates User-triggered installation and patching You control when the runtime and profiles update

A concrete scenario: someone who keeps a chat client, a project tracker and a webmail account in Firefox tabs can install each as a separate PWA, get distinct taskbar icons, and stop hunting through tabs. The trade-off is a second Firefox installation to maintain and update, plus the fact that each PWA is a full browser window rather than a lightweight tab.

Next step: check the project's user guide and FAQ at PWAsForFirefox before installing, since the setup order (runtime, then extension, then in-browser installation) matters. If you would rather avoid a separate runtime, compare with a browser that installs PWAs natively, such as Google Chrome or Microsoft Edge, where installation is a single menu action but you give up Firefox and its extensions.

What are the differences between PWAsForFirefox and native Firefox PWA support?

PWAsForFirefox exists precisely because Firefox itself does not offer native PWA installation. Firefox supports many of the underlying web APIs that PWAs rely on, but it lacks the piece that turns a website into a standalone system app — often called a Site Specific Browser (SSB). PWAsForFirefox fills that gap with a custom modified Firefox runtime, plus a command-line tool and a browser extension to install, manage and run PWAs as separate apps.

How they differ in practice

Aspect Native Firefox PWAsForFirefox
Install as standalone app Not supported Supported via modified runtime
App window Regular browser tab or window Own window, no tabs or address bar
Start/app menu and taskbar entry None Yes, per installed PWA
Isolation Shared browser profile Separate Firefox installation and profile(s)
Add-ons and Firefox features Available in the main browser Available inside installed PWAs
Management Not applicable CLI tool plus extension for install, manage, run

What this means for different users

If you only need a website open in a tab, native Firefox is simpler and requires nothing extra. If you want a site to behave like a desktop application — its own icon, its own window, no browser chrome — PWAsForFirefox is the option that provides it.

The trade-off is setup and maintenance. PWAsForFirefox installs a separate Firefox runtime and keeps PWA profiles apart from your main browsing profile. That isolation is useful for keeping work apps separate from personal browsing, but it also means a second installation to update and manage. The extension handles much of this from within Firefox, and the project notes support for user-triggered automatic installation and patching.

A practical starting point: pick one site you use daily, such as a webmail or chat service, install it through the extension, and see whether the standalone window suits your workflow before converting more. If you prefer keeping everything in one browser profile, native Firefox remains the lower-friction choice. For background on how PWAs are meant to behave across platforms, web.dev is a useful reference.

Can I use Firefox extensions and add-ons within installed PWAs?

Yes. PWAsForFirefox is built around a modified Firefox runtime, and its feature list explicitly includes support for all Firefox add-ons and extensions inside installed PWAs. That is a meaningful difference from the browser's own limited PWA behavior, which it addresses by adding a standalone, app-like installation layer.

What that means in practice

  • Each installed PWA runs in its own isolated Firefox installation and profile, so extension state travels with that PWA's profile rather than your main Firefox profile.
  • Because the runtime is Firefox, Firefox's built-in features (for example, container-like profile separation, developer tools, and privacy settings) remain available in the PWA window.
  • PWAs launch without tabs or an address bar, so extensions that depend on toolbar buttons may have limited visible UI even though they still run.

A concrete scenario

Suppose you install a chat or documentation site as a PWA and want your password manager, an ad blocker, and a translation extension available only there. You would install those add-ons into that PWA's profile. Your main Firefox browsing stays untouched, and the PWA keeps its own extension set.

Decision criterion

Choose this approach if you want Firefox's extension ecosystem inside app-like windows and are comfortable with per-PWA profiles. If your main goal is simply having a site open in its own window without managing separate profiles, Firefox's own window features may be enough.

Next step: check the project's user guide and FAQ on PWAsForFirefox before installing, since setup involves a browser extension plus a native runtime.

How do I troubleshoot common issues with PWAsForFirefox?

Start with the project's own help resources, then narrow down whether the problem is in installation, the PWA's own profile, or the underlying Firefox runtime. PWAsForFirefox is a tool for installing, managing and running Progressive Web Apps in Mozilla Firefox, using a modified Firefox runtime plus a command-line tool and a browser extension. Because several moving parts are involved, most issues trace back to one of those layers rather than to the website itself.

First stops

  • Check the project's FAQ and help section before changing anything; common setup questions are usually answered there.
  • Follow the user guide for the exact installation and usage steps, since skipping the extension setup or the in-browser installation flow is a frequent cause of a PWA not appearing.
  • If the extension is involved, install it first and follow the in-browser instructions, as the project recommends.

Match the symptom to the layer

Symptom Likely layer Practical check
PWA does not install or does not appear as an app Extension or install flow Re-run installation from the browser extension; confirm the site is being installed as a PWA rather than opened as a normal tab
PWA opens but looks like a normal browser window with tabs Runtime or profile Confirm you launched the installed app entry, not the main Firefox window; installed PWAs are meant to have no tabs or address bar
Login or site data missing in the PWA Isolated profile Remember PWAs use their own isolated Firefox profile, so they do not share cookies or sessions with your main Firefox
Extension or add-on behaviour differs inside the PWA Add-on support PWAs support Firefox add-ons and built-in features, but check whether the specific add-on needs configuration per profile
Updates or patching fail Runtime installation Use the user-triggered installation and patching flow described in the guide

A concrete troubleshooting sequence

  1. Reproduce the issue once, noting whether it happens in the main Firefox browser, in the installed PWA window, or during installation.
  2. Confirm the browser extension is installed and that you followed the in-browser installation instructions.
  3. Check the FAQ and help pages for your exact symptom.
  4. If the PWA runs but behaves oddly, test the same site in your normal Firefox profile to separate a site problem from a PWA profile problem.
  5. If installation or patching is the issue, re-run the user-triggered installation or patching step rather than manually editing files.

When to look beyond the tool

If the site fails in normal Firefox too, the problem is with the site or your network, not PWAsForFirefox. If only the installed app misbehaves, treat it as a profile or runtime issue. For background on what PWAs are and how they behave across browsers, see MDN Web Docs and web.dev. For Firefox itself, Mozilla is the authoritative source.

Related questions

More questions →
What is PWAsForFirefox?

PWAsForFirefox is a tool that lets Mozilla Firefox install, manage, and run Progressive Web Apps (PWAs) as standalone applications. It exists because Firefox supports many PWA-related web APIs but does not natively support installing a website as a standalone system app with an app-like experience — functionality often called a Site Specific Browser (SSB). The project works around this by creating a custom modified Firefox runtime, paired with a console tool and a browser extension.

How it works

The project does not add PWA installation to your existing Firefox profile. Instead, it sets up a separate, isolated Firefox installation and profile(s) dedicated to hosting the installed PWAs. A command-line tool and a browser extension sit on top of that runtime to install, manage, and launch the apps.

In practice, that means:

  • A command-line tool handles installing, managing, and running PWAs.
  • A browser extension lets you set up the native programs and install, manage, and run PWAs and their profiles directly from your main Firefox browser.
  • The isolated Firefox installation and profile(s) store the PWAs separately from your normal browsing setup.

What installed PWAs look like

Once installed, each PWA behaves more like a native application than a browser tab:

  • It gets its own start/app menu entry and taskbar icon.
  • It runs in its own window.
  • It has no tabs and no address bar, which gives it a cleaner, app-like feel.

Features

According to the project's feature list, PWAsForFirefox supports:

  • Installing, managing, and running PWAs in Firefox via the command-line tool.
  • Setting up native programs and managing PWAs and their profiles from the main Firefox browser via the extension.
  • Installing all websites as Progressive Web Apps, not just ones that formally declare PWA support.
  • All Firefox addons/extensions and built-in Firefox features inside the installed PWAs.
  • Automatic, user-triggered installation and patching of the installation and profile(s).

When to use it

PWAsForFirefox is relevant if you want app-like, standalone windows for web apps but prefer to stay on Firefox rather than switching to a browser with built-in PWA installation. It is a fit when you want:

  • Web apps to open in their own window without tabs or an address bar.
  • A separate environment for those apps, isolated from your regular Firefox profile.
  • The ability to install any website as an app, including sites that are not full PWAs.
  • Your existing Firefox extensions and features available inside those apps.

If you only need occasional access to a web app inside a normal tab, the extra setup of a separate runtime and profile is probably more than you need.

Getting started

The project's own guidance is to install the browser extension and follow the in-browser installation instructions, then consult the installation page for setup details and the user guide for day-to-day usage. If you run into setup or usage problems, the help section — especially the FAQ page — is the intended first stop.

Supporters

The project notes that packagecloud.io sponsors it by providing free hosting for its DEB and RPM packages, and it also credits SignPath among its supporters.

How to Install and Set Up PWAsForFirefox

PWAsForFirefox installs Progressive Web Apps as standalone apps in Mozilla Firefox by creating a separate, modified Firefox runtime alongside your normal browser. To set it up, install the browser extension first, then follow the in-browser installation instructions; the project's installation page and user guide cover the detailed steps. This is for Firefox users who want app-like, tab-free windows for web apps — it is not needed if you only want normal Firefox tabs.

What gets installed

The project is made up of three parts, and setup creates all of them:

  • A command-line tool — installs, manages, and runs PWAs in Firefox.
  • A browser extension — sets up the native programs and lets you install, manage, and run PWAs and their profiles from your main Firefox browser.
  • An isolated Firefox installation and profile(s) — a separate runtime that stores the PWAs, so your everyday Firefox profile is left alone.

Each installed PWA gets its own start/app menu entry and taskbar icon, opens in its own window, and has no tabs or address bar.

Setup steps

  1. Install the browser extension. The project's usage guidance says to start here.
  2. Follow the in-browser installation instructions. The extension walks you through setting up the native programs.
  3. Let it create the isolated runtime. Setup produces the separate Firefox installation and profile(s) that hold your PWAs. The project supports automatic, user-triggered installation and patching of the installation and profile(s).
  4. Install a PWA. Once set up, you install and manage PWAs from the extension in your main Firefox browser.
  5. Launch it like an app. The PWA appears in your start/app menu and taskbar and runs in its own window.

For step-by-step detail beyond the above, use the project's installation page and user guide.

Verify it worked

  • The PWA has its own entry in the start/app menu and a taskbar icon.
  • It opens in a dedicated window with no tabs and no address bar.
  • Your normal Firefox installation and profile are unchanged.

Common sticking points

  • Skipping the extension. The usage guidance is explicit: install the browser extension and follow the in-browser instructions rather than trying to set things up by hand.
  • Expecting it inside your normal Firefox. The PWAs live in the isolated Firefox installation and profile(s), not your everyday profile.
  • Setup or usage problems. Check the help section, especially the FAQ page, before troubleshooting further.

What you can install

The project supports installing all websites as Progressive Web Apps, and installed PWAs keep support for all Firefox addons/extensions and built-in Firefox features. A full feature list is on the project's dedicated features page.

Where to go next

  • Installation page — installing and setting up the project.
  • User guide and related pages — detailed usage instructions.
  • Help section and FAQ — setup problems and other questions.
  • Repository README — more project details.
What features does PWAsForFirefox offer?

PWAsForFirefox provides a command-line tool and a Firefox extension that together let you install, manage, and run Progressive Web Apps in Mozilla Firefox. It works by creating a separate, modified Firefox runtime where each installed PWA runs as a standalone app with its own window, start menu entry, and taskbar icon — filling the gap left by Firefox's lack of native PWA installation.

Core features

Command-line tool

A console tool for installing, managing, and running Progressive Web Apps in Firefox. This is the underlying mechanism the extension drives, and it can also be used directly.

Browser extension

An extension that lets you:

  • Set up the native programs the project relies on
  • Install, manage, and run PWAs
  • Manage PWA profiles directly from your main Firefox browser

The project recommends installing the browser extension and following the in-browser installation instructions.

Isolated Firefox installation and profiles

PWAsForFirefox creates a separate Firefox installation and profile(s) dedicated to storing the PWAs. This keeps installed apps isolated from your main browsing setup.

Standalone app experience

Installed PWAs:

  • Have their own start/app menu entry and taskbar icon
  • Live in their own window
  • Have no tabs and no address bar, for a more app-like feel

Broad compatibility

  • Support for installing all websites as Progressive Web Apps
  • Support for all Firefox addons/extensions and built-in Firefox features

Automatic installation and patching

Support for automatic, user-triggered installation and patching of the installation and profile(s).

Feature summary

Feature What it does
Command-line tool Install, manage, run PWAs in Firefox
Browser extension Set up native programs; install/manage/run PWAs and profiles from main Firefox
Isolated install & profiles Separate Firefox installation and profile(s) store the PWAs
Standalone app behavior Own start/app menu entry, taskbar icon, dedicated window, no tabs or address bar
Website support Install all websites as PWAs
Addon support All Firefox addons/extensions and built-in features
Automatic patching User-triggered installation and patching of install and profiles

Where to go next

  • Installation: check the installation page for setup details.
  • Detailed usage: see the user guide and related pages.
  • Problems or questions: check the help section, especially the FAQ page.
  • Full feature list: available on a dedicated features page.
Why Firefox Needs PWAsForFirefox to Install PWAs

Firefox supports many Progressive Web App APIs, but it does not support installing a PWA as a standalone system app with an app-like experience. That missing capability — often called a Site Specific Browser (SSB) — is exactly what PWAsForFirefox provides. It does this by creating a custom modified Firefox runtime, then adding a console tool and a browser extension to install, manage, and run PWAs.

What Firefox already does — and what it doesn't

Progressive Web Apps use web APIs and progressive enhancement to deliver a native app-like experience across platforms. Firefox handles a large share of those APIs. What it lacks is the packaging and launch layer: turning a website into its own installable app that opens in a dedicated window, appears in the start/app menu, and behaves like a desktop program rather than a tab.

That gap is the SSB feature. Without it, a site you use constantly still lives inside a normal browser window with tabs and an address bar.

How PWAsForFirefox fills the gap

PWAsForFirefox builds a separate, modified Firefox runtime and an isolated Firefox installation and profile(s) to store the PWAs. On top of that runtime it provides:

  • A command-line tool to install, manage, and run PWAs in Firefox.
  • A browser extension to set up native programs and to install, manage, and run PWAs and their profiles directly from the main Firefox browser.

The result is that installed PWAs get their own start/app menu entry and taskbar icon, live in their own window, and have no tabs or address bar — the app-like feel Firefox alone doesn't deliver.

What you get once a site is installed

Capability What it means in practice
Standalone window The PWA opens on its own, not as a tab
No tabs or address bar Cleaner, app-like interface
Start/app menu entry and taskbar icon Launches like a normal desktop app
Isolated installation and profile(s) PWAs are stored separately from your main Firefox
Any website installable Support for installing all websites as PWAs
Add-ons and Firefox features Support for all Firefox extensions and built-in features
Automatic installation and patching User-triggered installation and patching of the installation and profile(s)

When this is the right tool

Choose PWAsForFirefox if you want to keep using Firefox as your browser but still want certain sites — mail, chat, dashboards, docs — to run as standalone apps with their own window and launcher entry. It is also the practical route if you want those apps isolated from your main browsing profile while retaining Firefox add-on support.

If you are satisfied opening those sites as ordinary tabs, or you already use a browser that installs PWAs natively, the extra runtime and setup may not be worth it.

Getting started

The project's own guidance is to install the browser extension and follow the in-browser installation instructions, with the installation page covering setup details. For day-to-day use, the user guide and related pages cover the workflow. If setup or usage goes wrong, the help section — especially the FAQ page — is the first place to check.

Where to Get Help with PWAsForFirefox Problems

If you run into trouble installing or using PWAsForFirefox, start with the project's help section, and in particular its FAQ page. The site points to the FAQ as the first place to check for setup and usage problems, with the user guide and repository README as supporting references for more detail.

Help resources the project points to

The PWAsForFirefox site lists several places to look when something goes wrong:

  • Help section — the site's stated first stop for problems setting up or using the project, and for other questions about it.
  • FAQ page — called out specifically within the help section for common setup and usage questions.
  • User guide and related pages — the site directs you here for detailed usage instructions.
  • Repository README — described as the place for more details about the project.
  • About section — also offered for more background on the project.

Which resource to use for which problem

If your problem is about… Go to…
Setting up the project for the first time Installation page, then the user guide
Using PWAs day to day User guide and related pages
A recurring or common question FAQ page
Understanding what the project is or how it works About section and repository README
Anything else Help section

Before you dig in: the intended setup path

The site's usage guidance is to install the browser extension and then follow the in-browser installation instructions, with the installation page covering installation and setup in more detail. If you hit a problem, it helps to confirm you followed that path — extension first, then the in-browser steps — before assuming something is broken.

What the tool is, briefly

PWAsForFirefox is a tool to install, manage, and use Progressive Web Apps in Mozilla Firefox. Firefox supports many PWA APIs but does not support installing them as a standalone system app with an app-like experience — functionality often called a Site Specific Browser (SSB). The project creates a custom modified Firefox runtime so websites can be installed as standalone apps, and provides a console tool plus a browser extension to install, manage, and use them.

Knowing this matters for troubleshooting: installed PWAs run in an isolated Firefox installation and profile(s), have their own start/app menu entry and taskbar icon, live in their own window, and have no tabs or address bar. Problems that look like "missing" browser chrome are by design, not a fault.

Practical notes

  • The project supports installing all websites as PWAs, and supports all Firefox addons/extensions and built-in Firefox features — so if an extension behaves unexpectedly inside a PWA, that context is worth mentioning when you consult the FAQ or help section.
  • Installation and patching of the installation and profile(s) is automatic but user-triggered, which is useful to know if you are diagnosing a version or update issue.

The site does not describe support channels beyond these documentation resources, so the FAQ and help section remain the concrete starting points.

Website Overview

An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality. Page metadata, canonical configuration and social previews work together to provide more consistent search and sharing presentation.

Domain and Registration

Registered in 2016, this domain has about 10 years of history. That suggests continuity, although ownership and purpose may have changed. The domain uses the common .si extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by prasicek.si, indicating managed DNS hosting. DNS and provider evidence indicate traffic passes through the Cloudflare CDN, which may support caching and traffic distribution. MX records point to the filips.si email service. SPF and DMARC are configured. DKIM status is unknown. The lowest observed DNS TTL is 300 seconds.

TLS and Certificates

The public key uses EC with 256 bits. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued within the Google Trust Services cloud or CDN ecosystem. The certificate's total validity is about 90 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: HSTS, CSP, Permissions-Policy, clickjacking protection. CORS permits any origin to read this response. This is common for public resources; sensitive responses need narrower handling. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. The cf-ray response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers.

Technology Stack Analysis

The public page identifies Cloudflare without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

The Generator tag identifies mkdocs-1.6.1, mkdocs-material-9.7.7, making the publishing system easier to fingerprint. Twitter Card metadata is configured. JSON-LD includes Product or Offer data, potentially supporting eligible product search features. The title has 14 characters, within a common display range. A meta description is present, with 80 characters.

Hosting and Email

DNSprasicek.si
HostingCloudflare
Emailfilips.si
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) Location unknown Inferred 104.21.57.210

Registration details

RDAP / WHOIS

RegistrarAVANT.SI d.o.o.
Registered2016-06-24
Expires2027-06-24
Domain statusactive
Nameserversns1.neoserv.si、ns2.neoserv.si
DNSSECunknown

DNS records

DNS

TypeNameValueTTLPriority
Apwasforfirefox.filips.si.cdn.cloudflare.net104.21.57.210300—
Apwasforfirefox.filips.si.cdn.cloudflare.net172.67.149.243300—
AAAApwasforfirefox.filips.si.cdn.cloudflare.net2606:4700:3030::6815:39d2300—
AAAApwasforfirefox.filips.si.cdn.cloudflare.net2606:4700:3037::ac43:95f3300—
MXfilips.simail.filips.si3000
NSfilips.sins5.prasicek.si86400—
NSfilips.sins6.prasicek.si86400—
TXTfilips.siv=spf1 +a +mx +ip4:91.223.182.80 include:_spf.mail-prasicek.si +ip4:91.223.182.83 +ip4:91.223.182.84 ~all300—
CNAMEpwasforfirefox.filips.sipwasforfirefox.filips.si.cdn.cloudflare.net300—
DMARC_dmarc.filips.siv=DMARC1; p=quarantine; rua=mailto:[email protected]300—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectpwasforfirefox.filips.si
IssuerGoogle Trust Services
Valid until2026-11-12T22:48 · Remaining when checked: 34 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=utf-8
cache-controlpublic, max-age=0, must-revalidate
servercloudflare
x-content-type-optionsnosniff
referrer-policystrict-origin-when-cross-origin
access-control-allow-origin*

Identified technologies

Cloudflare

Pages, Search and Sharing

Meta descriptionA tool to install, manage and use Progressive Web Apps (PWAs) in Mozilla Firefox
Canonical URLhttps://pwasforfirefox.filips.si/
LanguageEnglish (default)
Twitter Cardsummary_large_image

No rules found

User reviews (0)

  • No reviews yet.