What it Checks
The parser fetches the URL and reads it as RSS 2.0, RSS 1.0 (RDF), Atom or JSON Feed, whichever the document is. It shows the feed's title, link, description, language, last update, content type and size, how often it publishes, then every item with its title, link, date, author, categories, id, enclosure (podcast audio) and a plain-text summary.
It also validates the feed against what readers rely on: the required elements of the format (an RSS channel's title, link and description; Atom's id, title and updated date), an id on every item and no id used twice, dates that parse and follow the format (RFC 822 for RSS, RFC 3339 for Atom and JSON Feed), no dates in the future, absolute links, a self link, enclosure type and length, the content type and the size.
If the URL is an HTML page, the parser follows the first feed the page advertises with <link rel="alternate"> and lists the others, so a blog's home page is enough. A page that advertises none is tried at the usual addresses (/feed, /rss.xml, /feed.xml, /atom.xml, /index.xml, /rss, /feed.json).
Run a Test
- Paste the feed URL, or the URL of a page that links to its feed.
- Press Parse. The result opens with the count and format, for example 10 items in an RSS 2.0 feed., in green when the feed has no issues, amber with warnings and red with errors.
- Read the issues, then click an item to read its summary, or export the table.
Options
There is nothing to set: the format is detected from the feed. The items table has its own controls:
- Filter and sort. Search the items and sort by any column.
- Export. Download the items as CSV or Excel.
Reading the Result
- Feed: the HTTP status and the URL of the feed that was read.
- Title, Link, Language: from the channel (RSS) or the feed element (Atom).
- Updated: the feed's own date (
lastBuildDate,pubDateor Atomupdated). When the feed has none, the newest item date, marked (newest item). - Newest, Average gap: the newest item date and the average time between items (“7 days”, “8 h”).
- Issues: errors (the format or what readers rely on is broken, such as two items sharing one guid), warnings (read differently by some readers, such as an ISO date in an RSS feed) and notes, each with up to five of the items concerned.
- Other feeds on the page: the other feeds the page advertises (comments, podcast, JSON), each with a Parse button.
- Items: one row per item, with its guid (or id) and, for podcasts, the enclosure type and size. Dates are shown in your local time zone.
Where each column comes from:
| Column | RSS | Atom |
|---|---|---|
| Link | link, else guid | link rel="alternate", else the first link |
| Date | pubDate or dc:date | published, else updated |
| Author | author or dc:creator | every author name |
| Summary | description, else content:encoded | summary, else content |
Good to Know
- A file that isn't valid XML (or JSON), or has no
<rss>,<rdf:RDF>or<feed>root and no JSON Feed version, is reported as an error, and so is a feed that answers an HTTP error. - Feeds over 16 MB (long-running podcasts) are read up to 16 MB: the complete items in that part are listed and a warning says how many. The table shows up to 5,000 items.
- Requests come from this server. A site that blocks data-centre traffic can refuse the feed; the status shows what it answered.
- Feeds are fetched without checking robots.txt. To see whether crawlers may fetch a feed, use the robots.txt Tester and the robots.txt guide.
API
POST /api/rss
Send the URL of the feed or of a page that links to it. discovered is the feed URL found on the page, or null when the URL was a feed already; alternates lists every feed the page advertises. total is the number of items read (the items list stops at 5,000), bytes is null when the feed was cut at 16 MB (truncated), and stats.averageDays is the average gap between items.
curl -X POST https://plumb.reacthive.dev/api/rss \
-H "content-type: application/json" \
-d '{ "url": "https://wordpress.org/news/" }'{
"url": "https://wordpress.org/news/",
"discovered": "https://wordpress.org/news/feed/",
"alternates": [
{ "href": "https://wordpress.org/news/feed/", "type": "application/rss+xml", "title": "WordPress News » Feed" },
{ "href": "https://wordpress.org/news/comments/feed/", "type": "application/rss+xml", "title": "WordPress News » Comments Feed" }
],
"status": 200,
"contentType": "application/rss+xml; charset=UTF-8",
"bytes": 293639,
"truncated": false,
"feed": {
"format": "RSS 2.0",
"title": "WordPress News",
"link": "https://wordpress.org/news",
"description": "The latest news about WordPress and the WordPress community",
"language": "en-US",
"updated": "Wed, 21 Oct 2026 13:44:09 +0000",
"self": "https://wordpress.org/news/feed/",
"generator": "https://wordpress.org/?v=7.2-beta1-64675",
"image": "https://s.w.org/favicon.ico?2"
},
"total": 10,
"items": [
{
"title": "Critical PHP Security Release",
"link": "https://wordpress.org/news/2026/10/critical-php-security-release/",
"date": "Wed, 21 Oct 2026 13:44:09 +0000",
"author": "John Blackbourn",
"categories": "Security",
"description": "The PHP project has announced a security release that fixes two critical security vulnerab…",
"guid": "https://wordpress.org/news/?p=21835",
"enclosure": "",
"enclosureType": "",
"enclosureLength": ""
}
],
"issues": [],
"counts": { "errors": 0, "warnings": 0, "notices": 0 },
"stats": { "newest": "2026-10-21T13:44:09.000Z", "oldest": "2026-08-19T23:33:49.000Z", "averageDays": 6.95 }
}Each issue is { "severity": "error" | "warning" | "notice", "message", "count"?, "examples"? }, where examples are up to five titles of the items concerned.