Website profiles · Technology insights · Alternatives

feedflow.dev

Minimal RSS reader for people who want a clean, chronological timeline — no algorithms, no clutter, no noise. Available on Android, iOS, macOS, Windows, and Linux.

No paid content found Multilingual
Visit website
Profile views 5 Outbound visits 1 Normal
FeedFlow Full homepage screenshot

At a glance

Category
Software & Apps
Language
English
Paid-content signal
No paid content foundObserved
Registered
2023
Hosting
FastlyInferred
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 FeedFlow?

FeedFlow is a minimal RSS reader built around a plain chronological list of your feeds — no algorithmic ranking, no clutter. It's available across Android, iOS, macOS, Windows, and Linux, and it supports RSS, Atom, and OPML.

The core idea is that you read the open web the way you choose. Articles stay on your device or in a sync service you pick, and no account is required. Practical features include:

  • Reading options: open articles in your default browser or a dedicated one, switch to Reader Mode with adjustable text size, and prefetch full content for offline reading.
  • Sync flexibility: keep everything local, use iCloud on Apple devices, Dropbox or Google Drive for cross-platform sync, or connect self-hosted services like FreshRSS, Miniflux, Feedbin, or BazQux.
  • Organization: import/export via OPML, group feeds into categories, bookmark articles, block noisy keywords, and search across everything.

Who it suits: someone who wants a simple, portable reader without lock-in — whether migrating from another reader or trying RSS for the first time. The trade-off is deliberate: you won't find algorithmic recommendations or heavy social features, and sync depends on the service you configure.

Next step: if you currently use another RSS reader, export your feeds as an OPML file and import it into FeedFlow to test the migration in minutes. If you self-host, check the sync options against your existing server before committing.

How does FeedFlow sync feeds across devices without an account?

FeedFlow syncs by using services you already have, rather than its own account system. You choose a sync backend, and the app stores your feeds, read states and bookmarks there; each device points at the same backend and sees the same timeline.

Your options, as described on the site

  • iCloud — for Apple devices (iPhone, iPad, Mac).
  • Dropbox or Google Drive — cross-platform cloud sync, so you can mix Android, Windows, Linux and Apple devices.
  • Self-hosted services — FreshRSS, Miniflux, Feedbin and BazQux.
  • Local only — keep everything on the device, with no sync at all.

How this plays out in practice

If you only use Apple hardware, iCloud is the least-effort path: it's already on your devices and you don't install anything extra. If you mix platforms — say an Android phone and a Windows laptop — Dropbox or Google Drive is the simpler choice, since both have clients everywhere.

The self-hosted route suits people who already run a server or who don't want a cloud provider holding their reading history. It's also the option that keeps working if you later switch readers, because your subscriptions live in a service you control.

The trade-off to understand

There's no FeedFlow account, so there's no FeedFlow-side recovery. Your sync provider is the source of truth. If you use Dropbox and lose access to that account, or if you self-host and your server dies without backups, your read state and bookmarks go with it. Local-only mode is private but means each device is its own island.

A sensible next step

Decide by device mix first, then by privacy preference: iCloud for all-Apple, Dropbox or Google Drive for mixed platforms, a self-hosted service if you want control and already run one server. Before committing, export your current subscriptions as an OPML file from your existing reader — the site says OPML import and export is supported, so migrating is a matter of importing that file and letting the first sync populate your other devices.

How do I migrate my existing RSS subscriptions from another reader to FeedFlow?

Import an OPML file. FeedFlow supports OPML import and export, which is the standard format nearly every RSS reader uses to move subscriptions between apps.

Typical migration path

  1. In your current reader, find the export option (usually under Settings, Account, or Feeds) and export your subscriptions as an OPML file.
  2. Save that file somewhere you can reach from the device where you're setting up FeedFlow.
  3. In FeedFlow, use the import option and select the OPML file. Your feeds and their categories come across in one step.
  4. Check the result: confirm the feed count matches, and skim your categories to catch anything that landed in the wrong folder or didn't transfer.

What carries over, and what doesn't

Item Usually transfers Notes
Feed subscriptions Yes Core of the OPML file
Categories/folders Yes Preserved as feed groups
Read/unread state No OPML stores feeds, not reading history
Starred or saved articles No Lives in the old service, not the file
Keyword blocklists No Recreate these manually in FeedFlow

That last row is worth planning for. One Google Play reviewer specifically called out FeedFlow's word blocklist as a standout feature, so if you rely on filtering, budget a few minutes to rebuild that list after the import.

If you sync rather than stay local

FeedFlow can keep articles on your device or sync through iCloud, Dropbox, Google Drive, or a self-hosted service such as FreshRSS, Miniflux, Feedbin, or BazQux. If you already run one of those, the smoother route is often to point FeedFlow at that server instead of importing a file — your existing subscriptions and read state are already there. One Google Play reviewer, James J., reported that FeedFlow "works great with my FreshRSS server," which is the setup to copy if you're in that camp.

A quick decision rule

  • Coming from a standalone reader with no server: export OPML, import into FeedFlow, done.
  • Already running FreshRSS, Miniflux, Feedbin, or BazQux: connect FeedFlow to that account and skip the file.
  • Heavily invested in read/unread history or saved articles: keep the old reader active for a week or two while you confirm nothing important is missing.

For the exact menu labels on your platform, check FeedFlow directly, since the import screen differs slightly between Android, iOS, and desktop.

Can FeedFlow connect to my self-hosted FreshRSS or Miniflux server?

Yes. FeedFlow lists both FreshRSS and Miniflux among the self-hosted services it can sync with, alongside Feedbin and BazQux, and it also supports iCloud, Dropbox and Google Drive if you prefer cloud sync or no server at all.

What that means in practice

If you already run FreshRSS or Miniflux, FeedFlow acts as a client rather than a replacement: your server keeps the subscriptions and read state, and FeedFlow reads and syncs against it. That is the setup one Google Play reviewer, James J., describes as working well with their FreshRSS server.

A typical use: you self-host Miniflux on a small VPS, add FeedFlow on your phone and laptop, and your read/unread state follows you without either device needing to be awake.

How the sync options compare

Setup Best for Trade-off
Local only One device, maximum privacy Nothing syncs between devices
iCloud Apple-only households Doesn't help Android or Windows
Dropbox / Google Drive Mixed devices, no server to maintain Depends on a third-party cloud account
FreshRSS / Miniflux / Feedbin / BazQux People who already run or pay for a backend You maintain or pay for the server

Before you commit

Confirm two things: that your server is reachable from your devices (a self-hosted instance on a home network may need external access), and that your server version supports the API FeedFlow expects — FreshRSS and Miniflux both expose APIs for third-party clients, but older installs can behave differently. The page also notes OPML import and export, so you can move your feed list in or out in minutes if you want to test the app against your existing reader first. FeedFlow is available on Android, iOS, macOS, Windows and Linux, with no account required.

If you're starting from scratch and don't want to run a server, FreshRSS and Miniflux are the two projects named here; otherwise, try FeedFlow in local mode for a week before deciding whether sync is worth the extra setup.

How does FeedFlow compare to algorithmic news feeds for staying informed without noise?

FeedFlow's core difference is the ordering rule: your feeds appear in the order they were published, with no ranking, recommendations or engagement-driven selection. The site's own framing is "Just a list." Algorithmic feeds, by contrast, decide what you see based on predicted interest, so the same subscriptions can produce a different front page for every reader and every session.

What that changes in practice

  • Completeness over relevance. A chronological list shows everything you subscribed to, including the boring-but-important items an algorithm might bury. The trade-off is volume: you see the misses as well as the hits.
  • Predictability. You can estimate how long a reading session takes because the list doesn't grow with "suggested" items. With an algorithmic feed, session length is set by the platform, not by you.
  • Control sits with your subscriptions. Noise reduction comes from curation you perform — unsubscribing, categories, keyword blocking — rather than from a model guessing on your behalf.

Tools FeedFlow offers for cutting noise without ranking

The page lists categories, bookmarking for later, a keyword blocklist, and search across everything. The keyword blocklist is the closest thing to a filter, but it is explicit and rule-based: you decide what to mute, and you can see why something disappeared. That is a meaningful difference from a hidden relevance score. FeedFlow also imports and exports OPML, so you can move your subscription list in and out rather than rebuilding it.

Sync and platform trade-offs

FeedFlow runs on Android, iOS, macOS, Windows and Linux, and the page states no account is required. You can keep articles on-device or sync through iCloud, Dropbox or Google Drive, and it lists self-hosted options including FreshRSS, Miniflux, Feedbin and BazQux. For a reader who already runs a FreshRSS or Miniflux instance, that means the reading client and the server stay separate — you are not locked to one vendor's cloud. One Google Play reviewer, James J., specifically notes it "works great with my FreshRSS server"; that is his experience, and the practical implication is that self-hosters can keep their existing backend and change only the app in front of it.

Who benefits most

Situation Chronological reader (FeedFlow's model) Algorithmic feed
You follow 10–30 niche sources and want to miss nothing Strong fit Risk of silent omissions
You want a bounded daily reading session Manageable via categories and blocklists Harder to bound
You want discovery of new sources Weak — you find them yourself Strong
You care about not being profiled Strong, especially with local or self-hosted sync Usually weak

A concrete scenario

Suppose you follow a dozen industry blogs, three YouTube channels and a local news site. In an algorithmic app, the local news might surface only when it trends. In FeedFlow, it appears when published, and you can convert those YouTube channels to RSS — a feature one Google Play reviewer, isopod, calls out as a highlight, alongside the blocklist. Your job becomes triage: skim the list, bookmark what needs attention, block recurring keywords you never read.

Decision criterion

Choose the chronological model if your problem is missing things and you are willing to do your own curation. Choose an algorithmic feed if your problem is too much to read and you would rather delegate selection. FeedFlow's page is explicit that it takes the first position, so judge it on whether you want that responsibility.

Next step: list the sources you would genuinely miss if they were ranked away, then check whether FeedFlow's import path — OPML from your current reader — brings them across intact. If most of your current reading comes from recommendations rather than subscriptions, this model will feel sparse at first; if most comes from subscriptions, it will feel complete.

Does FeedFlow support offline reading and a distraction-free reader mode?

Yes. FeedFlow is built around a chronological list of your feeds, and its reading features are designed to work without a constant connection. According to the product page, you can prefetch full article content for offline reading, which is useful for commutes or flights. It also offers a Reader Mode that strips away page clutter and lets you adjust text size for a more comfortable, distraction-free view.

How the two features differ

Feature What it does Best for
Prefetch / offline reading Downloads full article content ahead of time so it is available without a connection Flights, subways, rural travel, or any spotty-signal situation
Reader Mode Displays the article in a clean, text-focused layout with adjustable text size Long reads, reducing visual noise, reading on small screens

Practical scenario

If you commute by train with unreliable signal, you would open FeedFlow while still on Wi-Fi, let it prefetch the articles you want, and then read them in Reader Mode during the trip. When you get back online, your read/unread state and bookmarks sync through your chosen service.

A trade-off to keep in mind

Offline reading depends on prefetching, so it works best when you plan ahead rather than expecting every article to be available the moment you lose signal. Reader Mode also depends on how well a given site exposes its full content; some publishers may not provide the complete text, so the offline copy could be partial.

Next step

Check FeedFlow's own documentation or app settings for how to enable prefetching and where to toggle Reader Mode, since those controls may sit in different menus on mobile versus desktop. If you already use a sync service, confirm it is one FeedFlow supports so your offline reading state carries across devices. FeedFlow is available at FeedFlow.

Related questions

More questions →
Can I import my existing RSS feeds into FeedFlow?

Yes. FeedFlow supports OPML import and export, so you can move your existing feeds from another RSS reader instead of re-adding them one by one. The site describes migration as taking "minutes," and OPML is the standard format most readers use for exactly this. The main condition is that your current reader can export an OPML file — if it can, the import path is straightforward.

How the import works

OPML is a plain file that lists your feeds (and usually their categories). FeedFlow's stated workflow is:

  1. Export from your current reader — look for an "Export OPML" or "Export feeds" option in its settings.
  2. Import into FeedFlow — FeedFlow accepts OPML on all platforms (Android, iOS, macOS, Windows, Linux).
  3. Organize after import — FeedFlow lets you group feeds into categories, so you can tidy up the structure once everything is in.

The same OPML support works in reverse: you can export from FeedFlow later, which matters if you ever want to switch again. FeedFlow frames this as "no lock-in, ever."

What carries over and what doesn't

Item Behavior
Feed subscriptions Imported via OPML
Categories Supported for organizing feeds; whether your old category structure survives depends on how your previous reader wrote the OPML
Read/unread state Not part of OPML — expect a fresh start on article status
Bookmarks FeedFlow has its own bookmarking; old bookmarks generally don't transfer through OPML

OPML is a feed-list format, not a full account backup, so treat the import as bringing your sources across, not your reading history.

After importing: what you can do

Once your feeds are in, FeedFlow's features apply to everything you brought over:

  • Search across everything — including imported articles, so an old feed is still findable.
  • Bookmark articles to read later.
  • Block noisy keywords with a word blocklist — one reviewer specifically called this out as rare among readers.
  • Read your way — open articles in your default browser or a dedicated one, use Reader Mode with adjustable text size, and prefetch full content for offline reading.

Sync choice affects the migration

FeedFlow doesn't require an account, and your articles stay on your device or in a sync service you choose. That choice interacts with importing:

  • Local only — import on each device separately.
  • iCloud — sync across Apple devices.
  • Dropbox or Google Drive — cross-platform cloud sync.
  • Self-hosted — FreshRSS, Miniflux, Feedbin, or BazQux.

If you already run one of those self-hosted services, importing into the service and pointing FeedFlow at it may be the cleaner route than importing per device. One Google Play reviewer noted it "works great with my FreshRSS server."

Practical notes

  • Check your old reader's export first. If it only offers a proprietary backup, you may need to convert it to OPML before importing.
  • YouTube channels are automatically converted to RSS feeds, per a reviewer — useful if part of your old subscription list was video.
  • Ratings as a rough signal: 4.7★ on Google Play and 4.5★ on the App Store, with reviewers repeatedly citing simplicity and cross-device sync.

If your goal is simply "get my feeds out of the old app and into FeedFlow without retyping them," OPML import is the supported answer, and the site's own framing is that it takes minutes.

What Is FeedFlow?

FeedFlow is a minimal RSS reader that shows your feeds as a plain chronological list — no algorithm, no ranking, no clutter. It runs on Android, iOS, macOS, Windows, and Linux, supports RSS, Atom, and OPML, and requires no account. It fits you if you want to follow the open web in publication order and keep your reading data local or in a sync service you already control.

What it does

The core idea is stated plainly on the site: "Just a list. Your feeds, in the order they were published." There is no recommendation engine and no engagement-driven ordering. What you get is the standard set of reader capabilities:

  • Reading: Open articles in your default browser, or pick a dedicated browser for reading sessions. A Reader Mode gives a distraction-free view with adjustable text size.
  • Offline: Prefetch full article content so you can read on a commute or flight without a connection.
  • Organizing: Import and export with OPML, group feeds into categories, bookmark articles for later, block noisy keywords, and search across everything.
  • Formats: RSS, Atom, and OPML.

Sync and data ownership

FeedFlow does not force you into one backend. You choose where your articles live:

Option What it covers
Local only Articles stay on your device
iCloud Sync across Apple devices
Dropbox or Google Drive Cross-platform cloud sync
Self-hosted FreshRSS, Miniflux, Feedbin, BazQux

The site describes this as "no lock-in, ever," and OPML import/export means you can migrate from another reader in minutes.

Platform and account requirements

  • Platforms: Android (Google Play, plus F-Droid), iOS (App Store), macOS (App Store), Windows (App Store), Linux (Flathub, plus Homebrew among additional download options).
  • Account: No account required.
  • Languages: 25+.

What users report

Reviews quoted on the site highlight the same themes: simplicity, cross-device sync, and the keyword blocklist. One Google Play reviewer notes it "automatically converts YouTube channels to RSS feeds," and another says it "works great with my FreshRSS server." Ratings shown are 4.7 on Google Play and 4.5 on the App Store.

Who it is for

Choose FeedFlow if you want a chronological, algorithm-free feed list, multi-platform coverage, and control over where your data is stored — local, a mainstream cloud drive, or your own server. If you need algorithmic discovery, social features, or a hosted service with no setup at all, this is not that kind of reader.

What Reading Features Does FeedFlow Offer?

FeedFlow's reading features are built around three things: opening articles the way you prefer, stripping pages down to readable text, and keeping full content available when you're offline. If you read on a commute, a flight, or anywhere with unreliable connectivity, the offline prefetch and Reader Mode combination is the part that matters most. If you mostly read at a desk with a stable connection, the browser choice and keyword blocklist will be the features you notice day to day.

Opening articles: your browser, your choice

FeedFlow doesn't force you into an in-app reading view. You can:

  • Open articles in your default browser — the same browser you use for everything else.
  • Pick a dedicated browser for reading sessions — useful if you want to keep feed reading separate from your everyday browsing, or if you prefer a specific browser's reader or extension setup.

This matters because it means FeedFlow doesn't trap your reading inside its own rendering engine. You keep whatever extensions, password managers, and reading tools you already trust.

Reader Mode: distraction-free text with adjustable size

Reader Mode strips an article down to its text, removing navigation, ads, sidebars, and other page furniture. Within it, you can adjust the text size to whatever is comfortable.

The practical use case: many feeds only publish a summary or excerpt. Reader Mode is how you get from that summary to the full article body without leaving the reading flow. Combined with the browser choice above, you can decide per-session whether you want the clean text view or the original page.

Offline reading: prefetch full content

FeedFlow can prefetch full article content so it's available without a connection. The site describes this as "perfect for commutes or flights" — the two scenarios where you know in advance you'll be offline.

How to think about it:

Situation What prefetch gives you
Flight or train with no signal Full articles already downloaded, readable in Reader Mode
Spotty mobile data Articles load instantly instead of stalling
Reading on a device without a data plan Content is there as long as you synced beforehand

The trade-off is storage and sync time: prefetching full content means more data downloaded per feed than headlines alone. If you follow many high-volume feeds, expect the prefetch to take longer and use more space.

Filtering noise: keyword blocklist

FeedFlow includes a word blocklist that hides articles containing keywords you specify. One reviewer on Google Play called this out specifically: "a highlight is definitely the word blocklist because not many readers have that."

Typical uses:

  • Block a recurring topic you don't care about (a sport, a stock ticker, a fandom).
  • Filter out spoilers or clickbait terms.
  • Cut down feeds that mix content you want with content you don't.

Because it works at the keyword level rather than per-feed, it's a blunt instrument — it will also hide legitimate articles that happen to mention the word. Use specific terms rather than broad ones.

Organizing what you read

Reading features sit alongside organization tools that affect how you get to articles in the first place:

  • Categories to group feeds.
  • Bookmarks to save articles for later.
  • Search across everything.
  • OPML import/export to move your feed list in or out.

Other reading-adjacent details

  • Formats supported: RSS, Atom, and OPML.
  • YouTube channels are automatically converted to RSS feeds, per a Google Play review.
  • No account required — articles stay on your device or in a sync service you choose.
  • Platforms: Android, iOS, macOS, Windows, Linux (including F-Droid and Homebrew as additional download options).
  • Ratings cited on the site: 4.7 on Google Play, 4.5 on the App Store.

Is it a fit for your reading habits?

  • Choose FeedFlow for offline reading if you regularly read without a connection and want full articles, not just headlines, waiting for you.
  • Choose it for browser flexibility if you refuse to read inside a locked-in app view.
  • Choose it for the blocklist if your feeds are noisy and you want a simple keyword filter.
  • Look elsewhere if you want algorithmic recommendations, social features, or a heavily designed in-app reading experience — FeedFlow's stated position is "just a list," chronological, no algorithms.
Which platforms does FeedFlow support?

FeedFlow runs on five platforms: Android, iOS, macOS, Windows, and Linux. If you read feeds on a phone, tablet, and desktop, you can install it on all of them and keep one consistent experience. The site states no account is required, and your articles stay on your device or in a sync service you choose.

Platform-by-platform availability

Platform Where to get it
Android Google Play, F-Droid
iOS App Store
macOS App Store
Windows App Store
Linux Flathub, Homebrew

The download page lists "Additional download options: F-Droid, Homebre…" — so F-Droid is the alternative Android source, and Homebrew is an additional Linux option alongside Flathub.

What "one consistent experience" means in practice

The site's claim is that the app looks and behaves the same across phone, tablet, and desktop. A Google Play reviewer (Raj T.) describes using it on phone, tablet, and desktop with synchronisation between devices, which matches the cross-platform pitch. If your setup spans, say, an Android phone and a Linux laptop, both are covered.

Choosing your install source

  • Android: Google Play is the default; F-Droid suits you if you prefer an open-source app repository.
  • Apple devices: iOS and macOS both come from the App Store.
  • Windows: distributed through the App Store rather than a standalone installer, based on the page.
  • Linux: Flathub is the primary route; Homebrew is listed as an additional option.

What to check before installing

Platform coverage is only half the decision — the other half is sync. FeedFlow supports local-only storage, iCloud for Apple devices, Dropbox or Google Drive for cross-platform cloud sync, and self-hosted services (FreshRSS, Miniflux, Feedbin, BazQux). If you want your Android phone and Linux desktop to share the same read state, pick a sync option that works on both rather than iCloud, which is Apple-only.

The app also imports and exports via OPML, so migrating from another reader takes minutes regardless of which platform you start on.

How FeedFlow Syncs Feeds Across Devices

FeedFlow does not force you into one sync model. You can keep everything local on a single device, sync through iCloud on Apple hardware, use Dropbox or Google Drive for cross-platform cloud sync, or connect to a self-hosted service such as FreshRSS, Miniflux, Feedbin, or BazQux. The right choice depends on how many devices you read on and whether you want your feed data sitting in someone else's cloud.

The sync options at a glance

Sync method Works across Account needed Data lives
Local only One device No On your device
iCloud Apple devices (iOS, macOS) Apple ID Apple iCloud
Dropbox Android, iOS, macOS, Windows, Linux Dropbox Dropbox
Google Drive Android, iOS, macOS, Windows, Linux Google Google Drive
FreshRSS / Miniflux / Feedbin / BazQux Cross-platform Per service Your server or the service

FeedFlow is available on Android, iOS, macOS, Windows, and Linux, so the sync method you pick also decides which of those platforms can see the same read state and subscriptions.

Choosing based on your situation

If you read on one device only

Stay local. FeedFlow requires no account, and your articles stay on your device. This is the simplest setup and the one to pick if privacy or offline use matters more than multi-device access. The trade-off is obvious: nothing follows you to a second device.

If you live entirely in Apple's ecosystem

iCloud is the natural fit. It syncs across Apple devices without adding a third-party account, and it keeps the setup inside the ecosystem you already use.

If you mix platforms

Dropbox or Google Drive is the cross-platform route. Because FeedFlow runs on all five major platforms, this is what lets a Windows desktop and an Android phone share the same feed list and read state. Pick whichever cloud account you already trust with your data.

If you want to own the backend

Point FeedFlow at a self-hosted or independent service: FreshRSS, Miniflux, Feedbin, or BazQux. This is the option for people who already run a feed server or want to avoid the big cloud providers. One reviewer noted it "works great with my FreshRSS server," which is the typical use case here.

What stays consistent no matter which you pick

  • No lock-in. FeedFlow states there is no lock-in, so you can change sync setups later rather than committing permanently.
  • OPML import and export. You can migrate from another reader in minutes, and move your subscriptions between setups.
  • Organization carries over. Categories, bookmarks, keyword blocking, and search work alongside whichever sync method you choose.

A practical way to decide

  1. Count your devices. One device means local-only is enough.
  2. Check the platforms. All-Apple points to iCloud; a mixed set points to Dropbox, Google Drive, or a self-hosted service.
  3. Decide who holds the data. If the answer is "nobody but me," go local or self-hosted. If convenience wins, use a cloud drive you already have.

Because the sync layer is swappable and there is no lock-in, this is not a permanent decision — you can start local and add sync later, or move from a cloud drive to your own server when your needs change.

Website Overview

The available information shows a mix of normal operation and configuration gaps. Depending on how the website is used, these gaps may affect secure access or the consistency of its public presentation.

Domain and Registration

Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The domain has about 3 years of registration history; its current configuration provides more context than age alone. The domain uses the common .dev extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by encirca.net, indicating managed DNS hosting. The CNAME points to prof18.github.io, associated with GitHub Pages. No MX record was found. A conventional explicit inbound-mail route is not configured. TXT records include verification markers for Google. Such markers may also remain after a service stops being used. DNSSEC signatures were not detected, so this additional DNS authenticity protection is not confirmed.

TLS and Certificates

The certificate uses an RSA 2048-bit public key, offering broad client compatibility. 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 by Let's Encrypt, commonly associated with automated certificate services. The certificate's total validity is about 89 days, consistent with a short renewal cycle.

HTTP and Browser Security

The checked browser-security headers were not detected, leaving fewer explicit browser-side safeguards. 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 x-cache, x-served-by, via 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 Fastly without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

The meta description has 163 characters and may be shortened in search results. The Generator tag identifies Hugo 0.166.0, making the publishing system easier to fingerprint. Twitter Card metadata is configured. JSON-LD includes Organization data, helping describe the organization as an entity. The page declares 12 language or regional alternatives using hreflang.

Hosting and Email

DNSencirca.net
HostingFastly
EmailUnknown
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) United States flagUnited States Inferred 185.199.108.153

Registration details

RDAP / WHOIS

RegistrarEnCirca
Registered2023-07-27
Expires2027-07-27
Domain statusclient transfer prohibited
Nameserversstandard3.encirca.net、standard4.encirca.net
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Aprof18.github.io185.199.108.1533600—
Aprof18.github.io185.199.109.1533600—
Aprof18.github.io185.199.110.1533600—
Aprof18.github.io185.199.111.1533600—
AAAAprof18.github.io2606:50c0:8000::1533600—
AAAAprof18.github.io2606:50c0:8001::1533600—
AAAAprof18.github.io2606:50c0:8002::1533600—
AAAAprof18.github.io2606:50c0:8003::1533600—
NSfeedflow.devstandard3.encirca.net86400—
NSfeedflow.devstandard4.encirca.net86400—
TXTfeedflow.devgoogle-site-verification=7HpumJnZYq-DbYAKOkkNI6voBuwTLyAZHLoKCmrbDKw300—
CNAMEwww.feedflow.devprof18.github.io600—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectwww.feedflow.dev
IssuerLet's Encrypt
Valid until2026-11-26T13:21 · Remaining when checked: 53 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=utf-8
cache-controlmax-age=600
serverGitHub.com
access-control-allow-origin*

Identified technologies

Fastly

Pages, Search and Sharing

Meta descriptionMinimal RSS reader for people who want a clean, chronological timeline — no algorithms, no clutter, no noise. Available on Android, iOS, macOS, Windows, and Linux.
Canonical URLhttps://www.feedflow.dev/
LanguageEnglish (default) · Multilingual
Twitter Cardsummary_large_image
All bots 1 allowed · 0 disallowed
  • Allow/

User reviews (0)

  • No reviews yet.