Website profiles · Technology insights · Alternatives

bmz.absolutezero.fyi

No paid content found
Visit website
Profile views 0 Outbound visits 0 Normal
Bookmark Manager Zero bmz.absolutezero.fyi Bookmark Manager Zero helps save, organize, tag, and search bookmarks or useful web links. ↗ Full homepage screenshot

At a glance

Category
Development
Language
English
Paid-content signal
No paid content foundObserved
Registered
2024
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 Bookmark Manager Zero?

Bookmark Manager Zero is a bookmark manager that treats link hygiene as part of organization. Beyond saving, tagging and searching bookmarks, it checks them for dead, parked or malicious URLs, and it works directly with your browser's native bookmarks rather than importing them into a separate account.

What it does

  • Organization: save, tag and search bookmarks and useful links.
  • Link validation: real-time checks that flag dead or parked links before you click them.
  • Malware screening: bookmarks are checked against multiple malware databases, with suspicious URLs flagged.
  • Native browser bookmarks: the Firefox and Chrome extensions read from and write to your browser's own bookmarks, so the browser stays the source of truth. There is no migration or lock-in, and edits made in either place appear in the other.
  • Optional mobile access: because mobile browsers and web apps can't reach native bookmarks, an optional GitLab sync sends bookmarks to a private repository in your own GitLab account using a personal access token. A web app and an Android wrapper around it can then read that repository.
  • Guarded sync: additions sync in both directions automatically, but anything that would delete, rename or move a bookmark pauses for confirmation and shows what would change and on which device.

Who it suits

The strongest fit is someone with a large, old bookmark collection who has stopped trusting it—link rot and hijacked domains are the everyday failure mode. The native-bookmark approach also suits people who don't want a second bookmark silo. The trade-off is that cross-device use depends on a GitLab account and token setup, which is more friction than a hosted service that syncs automatically.

As a next step, install the extension for your browser and run your existing collection through the validation check; the flagged links tell you quickly whether the security angle is worth the setup for your habits.

For adjacent options, compare with Raindrop.io if you want a hosted, cross-platform library and don't mind living inside its ecosystem.

How does Bookmark Manager Zero check my bookmarks for dead links and malware?

Bookmark Manager Zero checks bookmarks by running real-time link validation and multi-source malware detection against your saved links. According to the site, the browser extensions work directly with your native Firefox or Chrome bookmarks, so the checking happens on the bookmarks you already have rather than on a separate imported copy. The stated goal is to tell you which links are dead, parked, or dangerous before you visit them.

What the site says the checks cover

  • Dead links: flagged so you can spot bookmarks that no longer resolve.
  • Parked links: domains that have been parked, often a sign the original site is gone.
  • Suspicious URLs: flagged for closer inspection.
  • Malware: links are checked against multiple malware databases rather than a single source.

What it means in practice

For a reader with years of accumulated bookmarks, the value is in the "before you click" moment: an old bookmark to a defunct tool or a hijacked domain gets caught instead of silently sending you somewhere unexpected. Because the browser's native bookmarks remain the source of truth—edits flow both ways—the validation applies to the same list you already maintain, with no migration step.

Trade-offs to weigh

  • Privacy vs. checking: malware and dead-link checks require lookups against external databases, so some link data leaves your device. The site positions this as privacy-focused overall because bookmarks themselves stay in your browser and optional mobile sync uses your own private GitLab repository.
  • Coverage depends on the databases: multi-source detection is broader than one list, but no scanner catches everything; treat flags as prompts to verify, not final verdicts.
  • Mobile needs a bridge: mobile browsers can't read native bookmarks, so on-the-go checking relies on the optional GitLab sync setup.

Next step: if you want to test it, install the extension for your browser, let it scan your existing bookmarks, and review the flagged dead or suspicious entries first—those are usually the quickest wins for cleaning up an old collection.

Does Bookmark Manager Zero work with my browser's native bookmarks instead of importing them into a separate account?

Yes. Bookmark Manager Zero's browser extensions work directly with your native Firefox or Chrome bookmarks rather than moving them into a separate account. Your browser's bookmark store is the source of truth: the tool reads from it and writes back to it, so edits made in the browser's built-in bookmark manager show up in Bookmark Manager Zero, and changes made there are saved to the native bookmarks. No import or migration step is involved, and there's no lock-in.

Where this stops being true

The native-bookmark approach only applies to the desktop browser extensions. Mobile browsers and web apps can't read a browser's native bookmarks because of platform restrictions, so the web app and Android app need the optional GitLab sync. That syncs your bookmarks to a private repository in your own GitLab account via a personal access token, which the web and Android apps then read. The page also states that sync never silently deletes: additions travel both ways on their own, but anything that would remove, rename, or move a bookmark pauses for confirmation and shows exactly what would change and on which device.

What this means in practice

  • Desktop-only user: install the extension and keep using your browser's own bookmark manager alongside it; there's nothing to import and nothing to maintain separately.
  • You want bookmarks on your phone: you'll need the GitLab sync setup, which is a deliberate extra step rather than something the extension can avoid.
  • You already use a cloud bookmark service: this is the opposite model, since the page explicitly contrasts itself with services like Raindrop.io that host your bookmarks in their own ecosystem.

As a decision criterion: if your main concern is keeping bookmarks inside the browser you already use, this fits. If you need seamless phone access with zero setup, expect to configure the GitLab repository first. For general background on browser bookmark behavior, see Mozilla Support and Google Chrome Help.

How do I access my bookmarks on my phone or a public computer using GitLab sync?

Use the browser extension to keep bookmarks in your native Firefox or Chrome bookmarks, then turn on optional GitLab sync to reach them from a phone or public computer. Setup runs through a GitLab personal access token (PAT), and your bookmarks sync to a private repository in your own GitLab account. The web app and the Android app (a wrapper around the web app) then read from that repository, so the same bookmarks appear on phones, tablets and shared machines.

Steps

  1. Install the extension for your browser and confirm your existing bookmarks are being read from and written back to the browser's native bookmarks.
  2. Generate a GitLab personal access token with the access the sync needs, then connect it in Bookmark Manager Zero.
  3. Let the initial sync create the private repository and push your bookmarks.
  4. On the phone, open the web app or the Android app and connect it to the same repository with the token.
  5. On a public computer, use the web app in a private window, connect with the token, and sign out or clear the session when finished.

What to expect

Sync is two-way for new bookmarks, but destructive changes—removals, renames, moves—stop and ask first, showing what would change and on which device. A rename you make yourself syncs silently; one arriving from another device waits. Nothing destructive happens without your confirmation.

The token approach is the main trade-off in your favour on shared machines: you paste a PAT rather than your GitLab password, and you can revoke it later without touching your account credentials.

Decision criteria

  • Choose GitLab sync if you want mobile access without moving bookmarks into a hosted bookmark service; your browser bookmarks remain the source of truth.
  • Skip it if you only use one desktop browser—the extension already covers that case.
  • If you need bookmarks on iOS, check whether the web app covers your needs, since the dedicated app described is Android-only.

For a broader set of alternatives, GitHub hosts the extension repositories linked from the project, and GitLab is where the private sync repository lives.

What happens if syncing would delete or rename a bookmark across my devices?

Sync never deletes, renames or moves a bookmark silently. Anything destructive pauses and asks you first, showing exactly what would change and on which device.

How the confirmation works

  • Additions sync freely. New bookmarks travel in both directions on their own, so nothing you saved on one device goes missing on another.
  • Destructive changes wait. A deletion, rename or move that arrives from another device stops for your approval, because it would overwrite something you may have chosen yourself.
  • Your own edits go through. A rename you make yourself syncs without a prompt, since you clearly meant it.

A practical scenario

Say you tidy a bookmark's title on your laptop, then open the web app on your phone later. The rename you made is already applied; a conflicting rename pushed from the phone would have been held back until you confirmed it. That ordering matters if you edit the same bookmark in two places on the same day — expect a prompt rather than a silent winner.

Decision criterion

This design suits people who sync across devices they don't fully control, such as a public computer, and who would rather approve a few prompts than discover a vanished bookmark. If you prefer fully automatic two-way sync and rarely rename or delete, the prompts will feel like friction. Sync relies on a GitLab personal access token and a private repository in your own account, so the confirmation step is part of that setup rather than a separate toggle.

For a broader look at how this compares with hosted bookmark services, see Raindrop.io.

Can I use Bookmark Manager Zero without creating an account or paying for a subscription?

Yes. Bookmark Manager Zero is built around your browser's own bookmarks, so the core workflow needs no account and no subscription: you install the extension, and it reads from and writes back to your native Firefox or Chrome bookmarks. There is no separate service holding your data, so there is nothing to sign up for.

Where an account-like step appears

The optional mobile/web sync is the one part that involves credentials. It works through a GitLab personal access token, and bookmarks sync to a private repository in your own GitLab account. That is a free GitLab account you control, not an account on this product, and you can skip it entirely if you only use bookmarks on one desktop browser.

What this means in practice

  • Single desktop browser: install the extension, keep using your browser's bookmark manager, and get link checking and malware/dead-link flagging without any sign-up.
  • Phone or public computer access: you'll need the GitLab token route, since mobile browsers and web apps can't reach native bookmarks. That's a setup step, not a paid tier.
  • Privacy trade-off: local-only use keeps everything in the browser; syncing moves a copy into your own GitLab repo, which you administer.

If you want the simplest start, install the extension for your browser first and try it against your existing bookmarks before deciding whether the GitLab sync is worth the extra setup. For a broader set of privacy-minded tools, FMHY maintains a curated list.

Related questions

More questions →
How Bookmark Manager Zero Differs from Raindrop.io

Bookmark Manager Zero (bmz.absolutezero.fyi) keeps your browser's native bookmarks as the source of truth and adds link validation and malware checks on top, whereas Raindrop.io moves your bookmarks into its own hosted ecosystem. The practical difference: with Bookmark Manager Zero there is no migration and no lock-in, but mobile access depends on an optional sync you set up yourself through your own GitLab account. Choose Raindrop.io if you want a ready-made cross-device service out of the box; choose Bookmark Manager Zero if you want your browser bookmarks to stay authoritative and are willing to configure sync yourself.

Where the bookmarks actually live

This is the core split, and it drives everything else.

Dimension Bookmark Manager Zero Raindrop.io (as described on the BMZ site)
Where bookmarks are stored Your browser's native Firefox or Chrome bookmarks Raindrop.io's own ecosystem
Migration required None — reads from and writes back to native bookmarks Bookmarks move into the service
Lock-in None; browser bookmarks remain the source of truth Tied to the hosted service
Editing model Two-way: edits in either the browser manager or BMZ appear in the other Managed inside the service

With Bookmark Manager Zero, the browser extension works directly against your native bookmarks. Edit something in your browser's built-in bookmark manager and it shows up in Bookmark Manager Zero; make a change in Bookmark Manager Zero and it's saved to your browser's native bookmarks. That round-trip is the whole point — the site explicitly frames this as the opposite of services like Raindrop.io that "move your bookmarks into their ecosystem."

What Bookmark Manager Zero adds: link and safety checks

Organization alone isn't the differentiator. The site positions Bookmark Manager Zero as organization plus security: it automatically checks bookmarks against malware databases, detects dead links, and flags suspicious URLs, so you know which links are dead, parked, or dangerous before you visit them. Raindrop.io is presented on the BMZ site purely as an organization-focused service, so if link validation and multi-source malware detection are what you need, that's the gap BMZ is aiming at.

Mobile access: optional GitLab sync instead of a hosted account

Mobile browsers and web apps can't read your browser's native bookmarks due to platform restrictions, so Bookmark Manager Zero bridges that gap with optional GitLab sync rather than a hosted account:

  1. Generate a GitLab personal access token (PAT) in your own account.
  2. Connect Bookmark Manager Zero with that token.
  3. Your bookmarks sync to a private repository in your own GitLab account.
  4. The web app and the Android app (a dedicated wrapper around the web app) sync with that repository, giving you access on phones, tablets, or public computers.

The site's stated rationale for GitLab: it's free, secure, and quick to set up, and unlike Google or other OAuth-based options you never enter your actual login credentials on devices you don't fully trust — you paste a PAT instead. (GitHub was considered first, but its API made the integration impractical, per the site.)

Sync is deliberately non-destructive: new bookmarks travel in both directions on their own, but anything that would remove, rename, or move a bookmark stops and asks first, showing exactly what would change and on which device. A rename you make yourself syncs silently; one arriving from another device waits, because it could overwrite a choice you made.

How to decide

  • Pick Bookmark Manager Zero if you want your browser bookmarks to remain the source of truth, you don't want to migrate or accept lock-in, you value dead-link and malware flagging, and you're comfortable creating a GitLab PAT for mobile access.
  • Pick Raindrop.io if you'd rather have a hosted service handle storage and cross-device access without you configuring a sync repository.

One caveat to verify yourself: the BMZ page describes GitLab as free and setup as taking minutes, but it doesn't publish pricing or login requirements for Bookmark Manager Zero itself, so confirm current terms on the site before committing.

Does Bookmark Manager Zero Store My Bookmarks, or Use My Browser's Own?

Your browser's own bookmarks remain the source of truth. The Bookmark Manager Zero browser extension for Firefox and Chrome reads directly from your native bookmarks and writes changes back to them, so nothing is moved into a separate account or ecosystem. The only exception is optional GitLab sync, which you turn on yourself to reach your bookmarks from mobile devices or other computers.

How the extension handles your data

According to the project's own description, the extension works with your native Firefox or Chrome bookmarks rather than importing them into a hosted service. That means:

  • Reads from your browser: the extension pulls in whatever is already in your browser's bookmark manager.
  • Writes back to your browser: changes you make in Bookmark Manager Zero are saved to your browser's native bookmarks.
  • Stays in sync both ways: edit something in your browser's built-in bookmark manager and it appears in Bookmark Manager Zero; edit in Bookmark Manager Zero and it lands in your browser.

The practical result is that you can keep using your browser's bookmark manager as you always have, and the extension layers organization, tagging, search, and link checking on top of the same data.

What "no lock-in" means here

The project contrasts itself with services like Raindrop.io, which it says move your bookmarks into their ecosystem. With Bookmark Manager Zero, there is no migration step and no separate copy that becomes the "real" one. If you stop using the extension, your bookmarks are still exactly where they were: in your browser.

When GitLab sync comes in

Mobile browsers and web apps can't read your browser's native bookmarks because of platform restrictions. To bridge that gap, Bookmark Manager Zero offers optional GitLab sync:

  1. Generate a GitLab personal access token (PAT).
  2. Connect the extension using that token.
  3. Your bookmarks sync to a private repository in your own GitLab account.
  4. The web app and the Android app (a dedicated wrapper around the web app) sync with that same repository.

The project notes that GitLab was chosen partly because setup takes minutes and you never enter your actual login credentials on devices you don't fully trust — you paste a PAT instead. GitHub was considered first but its API made the integration impractical.

Sync is designed not to delete silently

The project states that sync never removes anything behind your back. New bookmarks travel in both directions on their own, but anything that would remove, rename, or move a bookmark stops and asks first, showing exactly what would change and on which device. A rename you make yourself syncs silently; one arriving from another device waits for confirmation because it could overwrite a choice you made.

Deciding whether this fits you

Your situation What to expect
You only use bookmarks on one desktop browser The extension alone is enough; your browser stays the source of truth and no sync is needed
You want bookmarks on your phone or another computer You'll need to set up optional GitLab sync with a personal access token
You want to avoid a hosted bookmark service This design keeps your data in your browser and, if you opt in, in your own GitLab account
You might stop using the tool later Your bookmarks remain in your browser; there's no export or migration step required

If your main concern is where your bookmarks live, the answer is simple: in your browser, under your control, with GitLab sync as an opt-in bridge for other devices rather than a requirement.

How Bookmark Manager Zero Checks Bookmarks for Dead or Dangerous Links

Bookmark Manager Zero (bmz.absolutezero.fyi) runs link checks automatically as part of managing your bookmarks: it validates links in real time to flag dead or parked pages, and it checks URLs against multiple malware databases to flag suspicious ones. The point is to stop you from blindly clicking an old bookmark and landing on a dead page, a parked domain, or something dangerous. These checks sit alongside the usual save, organize, tag, and search features rather than replacing them.

What the checks actually do

The site describes three distinct signals you get before visiting a link:

  • Dead links — pages that no longer resolve, so you know a bookmark has rotted before you waste a click.
  • Parked links — domains that now show a parking page instead of the content you originally saved, a common fate for old bookmarks.
  • Dangerous links — URLs flagged through multi-source malware detection, meaning the address is checked against more than one malware database rather than a single list.

The framing on the site is explicit: most bookmark managers only handle organization, while this one adds security on top, "automatically checking your bookmarks against malware databases, detecting dead links, and flagging suspicious URLs."

Why this matters for old bookmarks

Bookmarks accumulate and age silently. A link you saved years ago may now point to an expired domain, a squatted domain, or a page serving malware. Without a check, the only way to find out is to click — which is exactly the risk the tool is designed to remove. Because the validation is automatic and continuous rather than a one-time scan you trigger, the status of your saved links stays current as part of normal use.

How the checks fit with how bookmarks are stored

The security checks are worth understanding alongside the tool's storage model, because it affects what gets checked and where:

  • Browser-native storage. The Firefox and Chrome extensions read from and write back to your browser's own bookmarks. Your browser's bookmark store is the source of truth — edits in either direction stay in sync, with no lock-in or migration.
  • Optional GitLab sync for mobile. Mobile browsers and web apps can't reach native browser bookmarks, so the tool offers optional sync to a private GitLab repository in your own account using a personal access token. The web app and the Android app (a wrapper around the web app) then sync through that repository.
  • Guarded sync. Sync never silently deletes: additions travel both ways on their own, but anything that would remove, rename, or move a bookmark stops and asks first, showing what would change and on which device.

In practice, this means the link checks apply to the bookmarks you actually keep in your browser, and the same set can follow you to mobile through the GitLab path if you enable it.

What to expect and what to verify yourself

The site presents these as automatic capabilities, but it does not publish specifics such as which malware databases are used, how often links are re-checked, or how quickly a newly dead link is flagged. If those details matter to you — for example, if you need to know the exact detection sources for a security review — treat them as things to confirm in the app rather than assume from the description.

A reasonable way to evaluate it: install the extension for your browser, let it read your existing bookmarks, and look at how dead, parked, and flagged links are surfaced in the interface. That will show you both the coverage and the presentation, which the site's summary doesn't fully specify.

The tool is also noted as featured on FMHY, and its source is available via GitLab and Firefox/Chrome repositories, so you can inspect the implementation if the detection logic is a deciding factor.

What Is Bookmark Manager Zero (bmz.absolutezero.fyi)?

Bookmark Manager Zero is a privacy-focused bookmark management suite that works directly with your browser's native Firefox or Chrome bookmarks instead of moving them into a separate service. Beyond saving, organizing, tagging, and searching links, it automatically checks bookmarks for dead links and known malware, so you can see which saved URLs are broken, parked, or dangerous before clicking them. It is aimed at people who already keep bookmarks in their browser and want organization plus link safety without migrating to a hosted ecosystem.

How It Differs From Typical Bookmark Managers

Most bookmark tools treat organization as the whole job. Bookmark Manager Zero adds a security layer on top:

  • Real-time link validation — flags bookmarks that no longer resolve.
  • Multi-source malware detection — checks saved URLs against malware databases and flags suspicious ones.
  • Parked-domain detection — identifies links that now point to parked pages rather than the original content.

The practical effect: an old bookmark folder becomes something you can audit rather than blindly click through.

Your Browser Stays the Source of Truth

The browser extensions read from and write back to your native Firefox or Chrome bookmarks. There is no import step and no separate bookmark store to keep in sync manually:

  • Edit a bookmark in your browser's built-in manager, and the change appears in Bookmark Manager Zero.
  • Edit it in Bookmark Manager Zero, and it is saved to your browser's native bookmarks.

This is the main contrast with services like Raindrop.io, which move bookmarks into their own ecosystem. Here, there is no lock-in and no migration, because the browser's bookmark store remains authoritative.

Getting Bookmarks Onto Mobile

Mobile browsers and web apps cannot access native browser bookmarks due to platform restrictions. To bridge that gap, Bookmark Manager Zero offers optional GitLab sync:

  1. Generate a GitLab personal access token (PAT) in your own GitLab account.
  2. Connect Bookmark Manager Zero using that token.
  3. Your bookmarks sync to a private repository in your own account.
  4. The web app and the Android app (a dedicated wrapper around the web app) sync from that repository, giving you access on phones, tablets, or public computers.

The design choice matters for trust: you paste a PAT rather than entering your actual login credentials on devices you don't fully control, which is the stated reason GitLab was chosen over OAuth-based options like Google. The site notes GitHub was considered first but its API made the integration impractical.

Sync Safety Behavior

Sync is deliberately conservative about destructive changes. New bookmarks travel in both directions on their own, but anything that would remove, rename, or move a bookmark stops and asks first, showing exactly what would change and on which device. A rename you make yourself syncs silently; one arriving from another device waits for confirmation, since it would overwrite a choice you may have made intentionally.

What You Get

Component What it is
Firefox extension Works with native Firefox bookmarks
Chrome extension Works with native Chrome bookmarks
Web application Browser-based access, syncs via GitLab
Android app Wrapper around the web app

Source code is hosted on GitLab (Firefox and Chrome repos are linked from the site), and the project has been featured on FMHY.

Who It Suits

Choose Bookmark Manager Zero if you keep bookmarks in Firefox or Chrome, want to stay in that system, and want dead-link and malware checks as part of managing them. If you need a fully hosted, cross-platform bookmark service with its own storage, this tool's browser-native approach is a deliberate limitation rather than a gap — and mobile access depends on setting up GitLab sync yourself.

How Bookmark Manager Zero Syncs Bookmarks to Mobile with GitLab

Bookmark Manager Zero gets bookmarks onto your phone by syncing them through a private GitLab repository in your own account. You connect the app with a GitLab personal access token (PAT), your bookmarks are written to that private repo, and the web app or Android app then reads from it on any device. This is an optional step: on desktop, the browser extensions work directly with your native Firefox or Chrome bookmarks and need no sync at all. GitLab sync exists because mobile browsers and web apps can't access native browser bookmarks due to platform restrictions.

Why GitLab instead of a built-in account

The project chose GitLab because it is free, secure, and takes minutes to set up — you only generate a personal access token. Unlike Google or other OAuth-based sync options, you never enter your actual login credentials on devices you don't fully trust. That matters if you're syncing on a public computer or a tablet you share.

GitHub was considered first, but per the project's own notes its API made the integration impractical.

What you need before starting

  • A GitLab account.
  • A GitLab personal access token with access to create and write to a private repository.
  • Bookmark Manager Zero installed in Firefox or Chrome on your desktop (the source of your bookmarks), or bookmarks already present in the web app.
  • The web app open, or the Android app installed (it is a dedicated wrapper around the web app).

Step-by-step setup

  1. Generate a GitLab personal access token. In your GitLab account settings, create a token with the scopes needed to create a private repository and read/write its contents. Copy the token — you won't see it again.
  2. Connect Bookmark Manager Zero to GitLab. In the app's sync settings, paste the PAT. The app uses it to create or access a private repository in your own GitLab account.
  3. Run the first sync from your desktop. Your bookmarks are written to that private repository. Because the browser extension treats your native bookmarks as the source of truth, this pushes what's already in your browser.
  4. Open the web app or Android app on your phone or tablet. Sign in to the same sync setup and point it at the same repository. Your bookmarks download to the device.
  5. Verify. Add or rename a bookmark on one device, sync, and confirm it appears on the other. Check that the repository in GitLab is private and contains your bookmark data.

How sync handles changes (and why nothing disappears silently)

Sync is two-way, but it is deliberately cautious about destructive operations. New bookmarks travel on their own in both directions. Anything that would remove, rename, or move a bookmark stops and asks first, showing exactly what would change and on which device.

The logic behind that: a rename you make yourself syncs silently, because you clearly meant it. A rename arriving from another device waits for confirmation, because it would overwrite something you may have chosen deliberately. Nothing destructive happens without you seeing it.

This is the main thing to expect in practice — the first sync after editing on two devices may prompt you to confirm changes rather than applying them automatically.

Common snags

  • Token scope too narrow. If the repository can't be created or written to, regenerate the PAT with broader repository permissions.
  • Confirmation prompts on sync. These are expected, not errors. Review the listed changes and approve them.
  • Expecting mobile to read native bookmarks. It can't — mobile browsers block that access. GitLab sync is the bridge, so set it up before relying on the phone app.
  • Trusting a shared device. The PAT is the credential on that device, not your GitLab password. Revoke the token in GitLab if you used a public computer.

Is this the right setup for you?

Use GitLab sync if you want bookmarks on phones, tablets, or public computers and are comfortable creating a token and a private repo. Skip it if you only use Bookmark Manager Zero on one desktop browser — the extension already reads and writes your native bookmarks with no lock-in or migration.

Website Overview

Several search or sharing settings need attention. Together they may make snippets, preview images or preferred URLs less consistent across platforms. An active inbound-mail setup with incomplete authentication may leave the domain more open to impersonation. Provider hosting alone does not close that gap.

Domain and Registration

Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The domain has about 2 years of registration history; its current configuration provides more context than age alone. The registrar is Porkbun LLC, a widely used domain service provider. The domain uses the common .fyi extension, which is not an independent safety signal.

DNS and Email

The observed email authentication setup is incomplete: DMARC is missing. Nameservers are provided by Cloudflare, indicating managed DNS hosting. MX records point to the Zoho Mail email service. No CNAME was found; the observed records resolve directly to addresses. TXT records include verification markers for Google. Such markers may also remain after a service stops being used.

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

No homepage title was detected; search engines may construct one from other page content. No homepage meta description was detected, leaving snippet selection more dependent on page text. No homepage canonical URL was detected. If duplicate URLs exist, consolidation may be less explicit. No Open Graph metadata was detected, so social previews may depend on platform inference. The observed directives allow indexing and link following.

Hosting and Email

DNSCloudflare
HostingCloudflare
EmailZoho Mail
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) Location unknown Inferred 104.21.86.228

Registration details

RDAP / WHOIS

RegistrarPorkbun LLC
Registered2024-10-05
Expires2027-10-05
Domain statusclient delete prohibited、client transfer prohibited
Nameserversalberto.ns.cloudflare.com、jule.ns.cloudflare.com
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Abmz.absolutezero.fyi104.21.86.228300—
Abmz.absolutezero.fyi172.67.137.109300—
AAAAbmz.absolutezero.fyi2606:4700:3030::ac43:896d300—
AAAAbmz.absolutezero.fyi2606:4700:3031::6815:56e4300—
MXabsolutezero.fyimx.zoho.com30010
MXabsolutezero.fyimx2.zoho.com30020
MXabsolutezero.fyimx3.zoho.com30050
NSabsolutezero.fyialberto.ns.cloudflare.com86400—
NSabsolutezero.fyijule.ns.cloudflare.com86400—
TXTabsolutezero.fyigoogle-site-verification=CBRskcQjLcj1lLWNGDlPFyP3GX4MY90jd1m8BxTH6Qg300—
TXTabsolutezero.fyiv=spf1 include:zohomail.com ~all300—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectbmz.absolutezero.fyi
IssuerGoogle Trust Services
Valid until2027-01-08T15:29 · Remaining when checked: 72 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 descriptionNot detected
Canonical URLNot detected
LanguageEnglish (default)
Twitter CardNot detected

Unknown

Unknown

No sitemaps found

User reviews (0)

  • No reviews yet.