Website profiles · Technology insights · Alternatives

rss-finder.rook1e.com

Discover RSS feeds from any website quickly and easily.

No paid content found
Visit website
Profile views 8 Outbound visits 2 Normal
RSS Finder Full homepage screenshot

At a glance

Category
Development
Language
English
Paid-content signal
No paid content foundObserved
Registered
2019
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 RSS Finder?

RSS Finder is a simple web tool for discovering RSS feeds on a given website. You enter a site's URL, and it scans that site to surface the RSS feed or feeds it can find. Its purpose is to solve a common annoyance: many sites still publish RSS but no longer advertise it with a visible feed icon, so the feed exists but is hard to locate manually.

RSS Finder

H3 How you would use it

A typical use is when you want to follow a site in a feed reader instead of checking it by hand:

  1. Copy the homepage or section URL of the site you care about.
  2. Paste it into RSS Finder and run the search.
  3. Take the feed URL it returns and add it to your RSS reader.

This is most useful for blogs, news sites, documentation sites and personal pages that have feeds but bury or omit the link. It is less useful for sites that genuinely have no feed, or for platforms whose content is only available through a login or app.

H3 What to keep in mind

The tool reports what it can detect from the page, so results depend on the site's structure. A feed may exist at a nonstandard address that isn't discovered, and a site may expose multiple feeds — for example, one for the whole site and separate ones for categories or tags. If the first result isn't what you want, try the URL of the specific section you're interested in rather than the homepage.

As a next step, once you have a feed URL, paste it directly into your reader's "add subscription" field; if it doesn't validate there, the site may have changed its feed setup, and you can retry with a more specific page URL.

How do I find the RSS feed for a website that doesn't show a feed link?

Paste the site's URL into RSS Finder and it will look for feeds the site doesn't advertise. That's the quick answer for the common case: a blog, news site or podcast page that publishes a feed but hides the link, or omits the <link rel="alternate"> tag your browser and feed reader rely on.

The tool's page is deliberately minimal — a URL field and a "Find RSS" button, with a link to its GitHub project. It takes a website address and reports the feeds it discovers, so you don't have to guess paths or read page source yourself.

When this is the right first move

  • You want a feed for a site you already read in a browser, and no orange RSS icon appears.
  • You're building a reader setup and want to add several sites quickly.
  • The site is a standard publishing platform (WordPress, Ghost, Substack-style newsletters, podcast hosts) where a feed almost certainly exists at a predictable path.

When it won't help

A finder can only report a feed that exists and is reachable. If a site never published one, or deliberately removed it, no tool will conjure it. Sites behind a login, or feeds restricted to subscribers, also stay out of reach. In those cases your options are a third-party service that generates a feed from a page, or accepting that the site isn't feed-friendly.

Checks worth doing yourself

If the finder comes up empty, spend two minutes on the usual suspects before giving up:

  1. Try the homepage, not a deep article URL — feeds are usually site-wide.
  2. Test the common paths directly in your browser: /feed, /rss, /feed.xml, /atom.xml, /index.xml, /rss.xml.
  3. View the page source (Ctrl+U or Cmd+Option+U) and search for application/rss+xml or application/atom+xml — the address is right there in the href.
  4. Check the site's footer or sidebar for a "Subscribe" or "Follow" link; some sites label the feed without the standard icon.

A practical example: you find a small research blog with no visible subscribe option. You paste the domain into RSS Finder, get a feed URL back, and add it to your reader. Six months later the author switches platforms, the old path 404s, and your reader shows nothing new — so it's worth re-checking the feed URL whenever a site you follow goes quiet, rather than assuming the writer stopped.

Can RSS Finder discover feeds from sites that use Cloudflare or other bot protection?

RSS Finder is unlikely to work reliably on sites that sit behind Cloudflare or similar bot protection. The tool works by fetching the target page and looking for feed links, so anything that blocks automated requests will usually stop it before it can read the page. RSS Finder

What typically happens

  • Cloudflare's challenge page returns a JavaScript or CAPTCHA interstitial instead of the real HTML, so there are no feed links to find.
  • Rate limiting or IP reputation blocks may return a 403 or an empty response.
  • Some protected sites pass through if the protection is lenient, the page is cached, or the feed is served from a separate, unprotected path.

Practical workarounds

  1. Try the common feed paths directly before assuming there is no feed: /feed, /rss, /rss.xml, /atom.xml, /feed.xml, /index.xml.
  2. Check the page source manually in your browser for application/rss+xml or application/atom+xml link tags. If you can see the page, you can see the feed link even when a tool cannot.
  3. Look for a newsletter or feed page the site publishes separately, which may not be behind the same protection.
  4. Use a reader that fetches feeds server-side from a different network if the block is IP-based rather than a hard challenge.

Decision criterion

If a site actively challenges automated clients, treat feed discovery as a manual task rather than a tooling problem. If it only rate-limits, retrying later or from a different network often succeeds.

Is there a browser extension or bookmarklet version of RSS Finder?

No browser extension or bookmarklet version is described on the RSS Finder site. The page presents RSS Finder as a web tool: you enter a website URL, it discovers that site's RSS feeds, and the page also links to a GitHub project. Nothing in the available page evidence mentions an extension, bookmarklet, or installable browser add-on.

If you specifically want one-click feed discovery from the toolbar, treat that as a separate requirement rather than assuming this tool provides it. A practical approach:

  • Use RSS Finder as a quick web-based lookup when you already have a URL.
  • If you want browser-level convenience, check your browser's extension store for feed-discovery add-ons and verify they are actively maintained.
  • Alternatively, many feed readers accept a site's main URL and attempt to locate the feed themselves, which removes the separate discovery step.

For a reader scenario: if you regularly subscribe to new sites while browsing, a reader that auto-detects feeds may save more time than a dedicated finder page. If you only occasionally need to inspect a site's feeds, the web tool is sufficient and avoids installing anything.

What should I do if RSS Finder returns no feeds for a site I know has one?

If RSS Finder returns no feeds for a site you know publishes one, the most common cause is that the feed is not declared where the tool looks. RSS Finder scans a page for feed links it can discover; it does not crawl every possible path or guess hidden URLs.

Work through these checks in order:

  1. Look for the standard feed paths. Try appending common feed locations to the site's domain, such as /feed, /rss, /rss.xml, /feed.xml, /atom.xml, or /blog/feed. Many publishers keep a feed live at a predictable path even when the visible page does not advertise it.
  2. Check the page source for a feed link. Open the site's HTML and search for application/rss+xml or application/atom+xml. If a <link rel="alternate"> tag exists, copy its URL directly. If it does not, the feed is effectively undiscoverable to automated tools, even though it works in a reader.
  3. Try a section-specific page. Large sites often publish feeds for categories, authors or tags rather than the homepage. Run RSS Finder on a blog index or section page instead of the root domain.
  4. Confirm the feed is still alive. Paste a candidate URL into a feed reader. A 404, a redirect to an HTML page, or a login wall means the feed has moved or been retired, not that the finder failed.
  5. Watch for blocking. Some sites serve different HTML to automated requests. If the page loads normally in your browser but returns nothing in a tool, that is a likely explanation.

Practical next step: once you have the working URL, add it manually to your reader and keep it. If the site is one you follow closely, a browser extension that detects feeds as you browse can catch ones that only appear on certain pages.

For broader discovery beyond a single site, Feedly and Inoreader both let you paste a site URL and will attempt to locate a feed, which is a useful second opinion when one tool comes up empty.

How does RSS Finder compare to using a website's sitemap or page source to locate feeds?

RSS Finder is a single-purpose lookup tool: you paste a website URL, and it tries to surface that site's RSS feeds for you. Compared with digging through a sitemap or reading raw page source, it trades manual inspection for an automated guess-and-check pass. RSS Finder

How the three approaches differ

Method What it actually checks Best for Main trade-off
RSS Finder The URL you submit, looking for declared or discoverable feed links Quickly testing one site, especially when you don't know where feeds live You rely on the tool's detection; it may miss feeds that aren't linked in the usual places
Page source The HTML <link rel="alternate"> tags and visible feed links Confirming exactly what the site itself declares Manual, and useless if the site hides or omits feed tags
Sitemap The site's list of URLs, sometimes including feed or XML endpoints Finding feeds on large or oddly structured sites Sitemaps are built for search engines, not readers; feeds are often absent

When each makes sense

Use RSS Finder first when you have a URL and just want an answer. It is the fastest option for a one-off check, and it saves you from scrolling through markup.

Fall back to page source when you want certainty. If the site declares a feed in its <head>, you will see it there, and you will also see the exact feed URL rather than a guess.

Use a sitemap when the site is large or when feed links are buried. A sitemap can reveal a /feed/ or /rss.xml path that the homepage never advertises, though it will not tell you whether the feed is still updated.

A practical next step

Pick a site you read regularly and try RSS Finder on it. Then open the page source and search for rel="alternate" to see whether the tool found the same feed. If the results match, you can trust the tool for quick checks; if they differ, treat page source as the more reliable source of truth. For sites where neither works, a sitemap is worth a look before you give up.

Related questions

More questions →
Why Can't RSS Finder Find an RSS Feed for My Website?

RSS Finder scans a URL you give it and reports any RSS feeds it can discover. If it comes back empty, the most common reason is that the site simply doesn't publish an RSS feed at all. Other frequent causes are that the feed exists but isn't linked from the page you scanned, that you entered the URL in a form the tool can't follow, or that the site blocks automated requests. Before assuming the tool is broken, check the site's homepage, its blog or news section, and the page source for a feed link.

The site may not have an RSS feed

Not every website publishes RSS. Many modern sites — especially those built as single-page apps or hosted on platforms that dropped feed support — never generate one. If the site has no feed, no finder can invent one.

How to confirm:

  • Look for a visible RSS icon or an "Subscribe" / "Feeds" link in the header, footer, or sidebar.
  • Check the blog or news section specifically; feeds are most often attached there rather than to the homepage.
  • Search the site for the word "RSS" or "feed."

If none of these turn up anything, the site most likely has no feed to find.

The feed exists but isn't linked from the page you scanned

RSS Finder discovers feeds by looking at what the page exposes — typically <link rel="alternate" type="application/rss+xml"> tags in the HTML head, or common feed paths. A feed can exist without being advertised on the page you entered.

Try scanning different URLs on the same site:

What to try Why it helps
The homepage Feed links are often declared site-wide in the head
The blog or news index Feeds are most commonly attached to article listings
A category or tag page Some sites expose per-section feeds only

If the homepage is a landing page with no feed link, the blog section may still have one.

The URL format or site access is the problem

The tool needs a reachable, correctly formatted URL. A few things can break the scan:

  • Missing or wrong scheme. Enter the full address, including https://. A bare domain or a typo can fail before the scan starts.
  • Login walls. If the feed sits behind authentication, RSS Finder can't reach it because it isn't logged in.
  • Bot blocking or rate limits. Some sites reject automated requests, so the scan returns nothing even though a feed exists.
  • Redirects. A URL that redirects heavily may not resolve to the page that carries the feed link.

If you suspect access restrictions, open the URL in a normal browser first. If it loads fine for you but not for the tool, the site is likely blocking automated access.

Check the page source manually

When RSS Finder comes up empty, the page source is the ground truth. This tells you whether a feed link is actually present.

  1. Open the site in your browser.
  2. View the page source (right-click → "View Page Source," or press Ctrl+U / Cmd+Option+U).
  3. Search the source for application/rss+xml or application/atom+xml.
  4. If you find a <link> tag, copy its href — that's the feed URL, and you can paste it directly into your reader.

If the source contains no such tag and no obvious feed path, the site isn't advertising a feed, and RSS Finder has nothing to report.

Common feed paths worth trying by hand

Some sites publish feeds at predictable locations without linking them prominently. You can test these directly by appending them to the site's domain:

  • /feed
  • /rss
  • /rss.xml
  • /feed.xml
  • /atom.xml
  • /blog/feed

If one of these returns XML in your browser, you've found the feed even though the finder didn't surface it.

What to do next

  • No feed anywhere: The site doesn't offer RSS. Consider a feed-generation service or a page-change monitor as an alternative, or check whether the site offers email newsletters instead.
  • Feed found in source or by path: Paste the direct feed URL into your RSS reader rather than relying on auto-discovery.
  • Blocked or login-gated: Try scanning a public section of the site, or fetch the feed URL directly if you have access.

RSS Finder reports what a page exposes; it can't create a feed that isn't there or get past a site that refuses automated requests. Working through the checks above will tell you which of those situations you're in.

Where to Access RSS Finder and Its Project Page

RSS Finder is available directly in your browser at rss-finder.rook1e.com — no installation, account, or sign-up required. The page presents a single Website URL input field and a Find RSS button as the main action, plus a GitHub Project link for source code and issue reporting. Use it when you want to quickly discover the RSS feeds behind any website.

How to Start Using RSS Finder

  1. Open your browser and go to rss-finder.rook1e.com.
  2. Paste the full URL of the website you want to check into the Website URL field.
  3. Click Find RSS.
  4. Review the feed results the tool returns for that site.

The expected result is a list of RSS feed URLs you can copy into your feed reader. If nothing is returned, the site may not publish a discoverable feed — see the troubleshooting section below.

What the Page Offers

Element Purpose
Website URL input Where you enter the site to scan
Find RSS button Runs the feed discovery
GitHub Project link Access the project source or report issues

The interface is intentionally minimal: one input, one button, one project link. There is no dashboard, saved history, or account layer described on the page.

Do You Need an Account or Install?

Based on the page content, no. RSS Finder runs as a web tool — you enter a URL and get results. There is no mention of registration, login, or a browser extension. That makes it suitable for one-off lookups rather than ongoing feed management.

If RSS Finder Can't Find a Feed

A missing result usually means one of these:

  • The site has no RSS feed. Many modern sites dropped feeds in favor of newsletters or social channels.
  • The feed exists but isn't advertised. Some sites host feeds at non-standard paths that aren't linked in the page's <head>.
  • The URL is wrong or incomplete. Try the exact page URL, including https://.

If you suspect a hidden feed, check common paths like /feed, /rss, or /feed.xml manually before concluding the site has none.

When to Use It

Reach for RSS Finder when you want a fast answer to "does this site have a feed?" without digging through page source. For building and maintaining a reading list across many sites, you'll still want a dedicated feed reader once you have the URLs.

How to Find a Website's RSS Feed with RSS Finder

RSS Finder (rss-finder.rook1e.com) is a browser-based tool that scans a website URL and lists the RSS feeds it can discover. Use it when a site doesn't advertise its feed link, when the feed isn't at the usual /feed or /rss path, or when you just want to confirm whether a feed exists before subscribing. You need the site's full URL and a place to paste the result (an RSS reader). No account or installation is described on the page.

Steps

  1. Open RSS Finder. Go to rss-finder.rook1e.com. The page shows a single input labeled for a website URL and a Find RSS button.
  2. Paste the full website URL. Enter the address including the scheme, e.g. https://example.com. Using the complete URL (with https://) is the safer input — a bare domain may or may not resolve the same way, so include the scheme when you can.
  3. Click Find RSS. The tool scans the site and returns the feeds it finds. Expect a short wait while it fetches and parses the page.
  4. Read the results. Each result is a feed URL. If the site exposes more than one (for example, a main feed plus a comments or category feed), you'll see multiple entries — pick the one that matches what you want to follow.
  5. Copy the feed link. The page includes a copy action ("Copied to clipboard!" confirms it). Copy the feed URL you want.
  6. Subscribe in your RSS reader. Paste that URL into your reader's "add feed / add subscription" field. The reader fetches the feed and starts showing items.

What to check if no feed appears

  • Try the exact page, not just the homepage. Some sites only expose feeds on section or blog index pages.
  • Include the scheme. https://example.com is a more complete input than example.com.
  • Confirm the site actually publishes a feed. Not every site does; a site with no feed will return nothing regardless of input format.
  • Re-check the copied link. Make sure you copied the feed URL from the results, not the site URL you typed in.

Quick reference

Step Action Expected result
1 Open rss-finder.rook1e.com Input field + Find RSS button
2 Paste full site URL (with https://) URL ready to scan
3 Click Find RSS List of discovered feed URLs
4 Copy a feed URL "Copied to clipboard!"
5 Paste into RSS reader Feed subscribed and loading items

The tool's page also links to a GitHub project, which is useful if you want to see how it works or self-host it. For everyday use, the five steps above are the whole workflow: paste a URL, find the feed, copy it, subscribe.

RSS Finder vs. manually finding RSS feeds: what's the difference?

RSS Finder is a web tool that takes a website URL and returns the RSS feeds it can discover, so you don't have to guess common feed paths or dig through page source yourself. Manual discovery is still worth knowing because it works when a tool returns nothing, and it helps you understand why a feed wasn't found. The practical approach is to try RSS Finder first, then fall back to manual checks if the result is empty or incomplete.

What each method actually involves

Using RSS Finder

RSS Finder presents a single input for a website URL and a "Find RSS" action. You enter the site's address, run the search, and the tool lists the feeds it finds for that site. The page also links to its GitHub project, so the discovery logic is open to inspection if you want to know how it works.

The workflow is: one input, one action, one list of results. There is no need to know where a site keeps its feed before you start.

Finding feeds manually

Manual discovery usually means one of these:

  • Checking the page source for a <link rel="alternate" type="application/rss+xml"> tag in the HTML head, which is how many sites advertise their feed to browsers and readers.
  • Guessing common paths, such as /feed, /rss, /rss.xml, /feed.xml, or /atom.xml, and appending them to the domain.
  • Looking for visible cues, like an RSS icon, a "Subscribe" link, or a feed link in the footer.

Each of these depends on the site having done something predictable. If it hasn't, you keep guessing.

Where the two approaches differ

Dimension RSS Finder Manual discovery
Starting point You only need the site URL You need the URL plus knowledge of where feeds usually live
Effort per site One input, one action Multiple steps: view source, test paths, inspect links
Speed on a familiar site Fast, but still a round trip through the tool Fast once you know the pattern
Speed on an unfamiliar site Consistent, since the tool does the scanning Slower, because you're testing possibilities one by one
Transparency Discovery logic is visible via the linked GitHub project You see exactly what you checked and why
Works when no feed exists Returns nothing, which is itself a signal Confirms the same thing, but only after you've exhausted the obvious paths
Best for Getting a result quickly across many sites Understanding a specific site's structure or troubleshooting

When RSS Finder is the better choice

Use the tool when your goal is speed and you don't care how the feed was located. It fits situations like:

  • You have a list of sites and want feeds for each without inspecting every one.
  • You're on a site with no visible RSS icon and don't want to read its HTML.
  • You want a quick check before deciding whether a site is worth subscribing to at all.

The trade-off is that a tool result is only as good as its discovery logic. If it returns nothing, you don't automatically know whether the site has no feed or the tool simply didn't find it.

When manual discovery is the better choice

Manual checking earns its place in three cases:

  1. The tool returns nothing. A site may still have a feed at a non-standard path or one that isn't advertised in the page head. Viewing the source and testing a few paths is the way to confirm.
  2. You need to understand the site. If you're building something that consumes feeds, knowing whether the feed is RSS or Atom, and where it lives, matters more than just having the URL.
  3. You're troubleshooting. When a feed exists but a reader won't accept it, checking the source tells you whether the link tag is malformed or missing.

The practical combination

Treat the two as a sequence rather than a competition:

  1. Enter the site URL in RSS Finder and run the search.
  2. If it returns one or more feeds, verify by opening one in a browser or feed reader.
  3. If it returns nothing, open the page source and search for application/rss+xml or application/atom+xml.
  4. If that's empty too, try the common paths (/feed, /rss, /rss.xml, /atom.xml) directly.
  5. If all of that fails, the site most likely doesn't publish a feed — which is a valid answer, not a failure of either method.

This order gets you a result fast in the common case and gives you a real diagnosis in the uncommon one.

What Is RSS Finder and What Does It Do?

RSS Finder is a free web tool that discovers RSS feeds for any website. You enter a site's URL, and it returns the feed addresses that site publishes. Use it when a site doesn't display an obvious RSS link, or when you want to subscribe to a site's updates in a feed reader instead of checking it manually.

How it works

RSS Finder takes a single input — a website URL — and scans that site for feed links. The page presents one field labeled "Website URL" and a "Find RSS" button. After you submit a URL, the tool reports the feeds it finds for that domain.

The tool is hosted at rss-finder.rook1e.com and is also linked to a GitHub project, so the source is available if you want to inspect how discovery works.

What an RSS feed is, and why finding one matters

An RSS feed is a machine-readable file a site publishes so that feed readers can pull its latest items. Once you add a feed URL to a reader, new posts appear there automatically — no need to revisit the site or rely on email newsletters or social media.

The practical problem RSS Finder solves: many sites still publish feeds but no longer advertise them with a visible RSS icon or link. The feed exists at a predictable path or is buried in the page's HTML, and a browser won't surface it. RSS Finder does that lookup for you.

When to use it

RSS Finder is a good fit if you:

  • Want to follow a blog, news site, or frequently updated site in a feed reader
  • Can't find an RSS link on the page itself
  • Are rebuilding a reading list and need to recover feed URLs for sites you used to follow
  • Want to check whether a site still offers a feed before giving up on it

It's less useful for sites that genuinely publish no feed, or for content locked behind a login — the tool can only report what the site exposes publicly.

How to use it

  1. Copy the URL of the site you want to follow (for example, the homepage or the blog section).
  2. Paste it into the "Website URL" field on rss-finder.rook1e.com.
  3. Select "Find RSS."
  4. Copy the feed address or addresses it returns.
  5. Paste that address into your feed reader's "add subscription" field.

Expected result: your reader begins showing that site's new items. If the tool returns nothing, the site likely doesn't publish a discoverable feed.

Common snags

  • Wrong URL scope. A homepage may expose different feeds than a subsection. If the homepage returns nothing useful, try the blog or news path directly.
  • Multiple feeds. Some sites publish several feeds (full posts, comments, categories). Pick the one matching what you want to follow.
  • No feed found. This usually means the site doesn't offer RSS, not that the tool failed. Some sites have dropped feeds in favor of newsletters or social accounts.
  • Feed stops updating. A feed URL can go stale if the site changes platforms. Re-run the lookup to get the current address.

The short version

RSS Finder is a single-purpose utility: give it a URL, get back the RSS feeds that site publishes. It's worth using whenever you want to follow a site in a reader but can't locate its feed yourself.

Website Overview

An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality. Several search or sharing settings need attention. Together they may make snippets, preview images or preferred URLs less consistent across platforms.

Domain and Registration

Registered in 2019, this domain has about 6 years of history. That suggests continuity, although ownership and purpose may have changed. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The registrar is Cloudflare, Inc., a widely used domain service provider. The domain uses the common .com 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 Cloudflare Email Routing 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 checked browser-security headers were not detected, leaving fewer explicit browser-side safeguards. 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. The Server header identifies cloudflare without an exact version.

Technology Stack Analysis

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

Search and Social Sharing

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 title has 48 characters, within a common display range. A meta description is present, with 55 characters. The observed directives allow indexing and link following.

Hosting and Email

DNSCloudflare
HostingCloudflare
EmailCloudflare Email Routing
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) Location unknown Inferred 104.21.83.71

Registration details

RDAP / WHOIS

RegistrarCloudflare, Inc.
Registered2019-11-30
Expires2026-11-30
Domain statusclient transfer prohibited
Nameservershenrik.ns.cloudflare.com、holly.ns.cloudflare.com
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Arss-finder.rook1e.com104.21.83.71300—
Arss-finder.rook1e.com172.67.217.46300—
AAAArss-finder.rook1e.com2606:4700:3035::ac43:d92e300—
AAAArss-finder.rook1e.com2606:4700:3036::6815:5347300—
MXrook1e.comroute1.mx.cloudflare.net30010
MXrook1e.comroute3.mx.cloudflare.net30041
MXrook1e.comroute2.mx.cloudflare.net30042
NSrook1e.comhenrik.ns.cloudflare.com86400—
NSrook1e.comholly.ns.cloudflare.com86400—
TXTrook1e.comgoogle-site-verification=pOsu6yAGIWxDV5TtuaqiFyhfRcrPe6Z5PskY7MF9Fkk300—
TXTrook1e.comv=spf1 include:_spf.mx.cloudflare.net ~all300—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectrss-finder.rook1e.com
IssuerGoogle Trust Services
Valid until2026-11-16T19:24 · Remaining when checked: 43 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html
servercloudflare

Identified technologies

SvelteKitCloudflare

Pages, Search and Sharing

Meta descriptionDiscover RSS feeds from any website quickly and easily.
Canonical URLNot detected
LanguageEnglish (default)
Twitter CardNot detected

Unknown

No rules found

No sitemaps found

User reviews (0)

  • No reviews yet.