Website profiles · Technology insights · Alternatives

pubpeer.com No paid content found

Categories: Science & Research

PubPeer enables scientists to search for their publications or their peers publications and provide feedback and/or start a conversation anonymously.

Visit website

Updated: 2026-09-21 13:12 Language: English (default) Access: Normal

Profile views 1 Outbound visits 0
PubPeer Full homepage screenshot

Related questions

More questions →
What Is PubPeer and How Does Post-Publication Peer Review Work?

PubPeer is a website where people can discuss published, peer-reviewed research after it has appeared in a journal. It is best understood as a platform for post-publication peer review: comments, questions, and criticism that happen after formal journal peer review is complete. A paper being discussed on PubPeer does not, by itself, mean the paper is wrong, retracted, or fraudulent. It means someone has raised a point that others can read, evaluate, and respond to.

How PubPeer Differs From Journal Peer Review

Traditional journal peer review happens before publication. A small number of invited reviewers assess a manuscript confidentially, and their comments usually stay private. PubPeer reverses several of those features:

Feature Journal peer review PubPeer discussion
Timing Before publication After publication
Visibility Confidential Public
Participants Invited reviewers Anyone who registers, often anonymously
Permanence Not usually published Comments remain visible
Outcome Accept, revise, or reject Conversation, correction, or further scrutiny
Moderation Editorial decision Limited; claims are not formally verified

The two are complementary, not equivalent. Journal review filters work before it enters the record. Post-publication review examines work that is already part of the record and may be widely cited.

How the Site Is Structured

PubPeer is organized around individual publications. Each paper has its own page, and discussion happens in a comment thread attached to that page.

  • Publication pages are linked to a specific article, usually identified by its DOI or other bibliographic details.
  • Comment threads hold the conversation. Comments can include text, links, and images such as figures or gel images.
  • Anonymous participation is a core design choice. Commenters can post without revealing their identity, which the site presents as a way to lower the risk of retaliation.
  • Search lets you look up a paper, an author, or a topic and see whether it has an existing thread.

Because comments are public and persistent, a thread can accumulate over months or years, with original authors, other researchers, and anonymous readers all taking part.

Who Participates, and Why Anonymity Matters

Participants typically fall into a few groups:

  • Researchers in the same field, who may recognize problems with methods, statistics, or figures.
  • The paper's own authors, who can respond, clarify, or dispute a point.
  • Readers and critics, including people doing image or data checks across many papers.
  • Journal editors and institutions, who sometimes monitor threads relevant to their publications.

Anonymity matters because public criticism of published work can carry professional risk. A junior researcher questioning a senior figure's paper may face pressure, and anonymity reduces that barrier. The trade-off is that anonymous comments carry no verifiable identity or credentials, so readers must weigh the argument on its merits rather than on who made it.

How to Interpret a Paper Being Discussed

The most common mistake is to treat any PubPeer thread as proof of misconduct. Threads vary widely in seriousness, and the type of concern matters.

Questions and clarifications

A commenter may simply ask how a method was applied, why a sample size was chosen, or what a figure shows. These are ordinary scientific questions and often get resolved in the thread.

Corrections and errors

Sometimes a thread identifies a genuine error: a mislabeled figure, a statistical mistake, or a duplicated image. The appropriate response is usually a correction or erratum, not necessarily a retraction.

Serious concerns and misconduct allegations

Some threads raise issues that, if confirmed, would be serious, such as image manipulation or data fabrication. These are allegations, not findings. Confirming them typically requires the journal, the authors' institution, or a formal investigation.

A practical reading checklist:

  1. Read the whole thread, not just the first comment.
  2. Check whether the authors responded and what they said.
  3. Distinguish a factual question from an accusation.
  4. Look for independent confirmation, such as a correction notice or retraction.
  5. Treat unresolved threads as open questions, not verdicts.

Limitations to Keep in Mind

PubPeer is a discussion venue, not a court or an editorial body. Several limitations follow from that:

  • No formal verification. Comments are not independently fact-checked before posting.
  • Limited editorial moderation. Content may be removed for legal or policy reasons, but the site does not adjudicate scientific disputes.
  • Anonymity cuts both ways. It protects legitimate critics and also allows unsupported claims.
  • Incomplete coverage. Only papers that someone chooses to discuss appear, so absence of a thread says nothing about a paper's quality.
  • Context can be missing. A comment may omit details that the authors consider important.

Practical Takeaways

If you encounter a PubPeer thread, use it as a starting point for your own judgment. Read the full conversation, note whether concerns were addressed, and check for official follow-ups such as corrections or retractions. If you are an author, you can respond directly in the thread to clarify or correct the record. If you are considering citing a paper with an active thread, weigh the specific concern against the rest of the evidence rather than treating the thread as a final verdict.

PubPeer's value is that it keeps scientific discussion going after publication. Its limitation is that it provides a forum, not a conclusion.

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 2012, this domain has about 14 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 Squarespace Domains II LLC, 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 Google Workspace email service. CAA records restrict which certificate authorities are authorized to issue certificates. No CNAME was found; the observed records resolve directly to addresses.

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 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 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 Google Analytics, Cloudflare without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

The homepage has an indexing or crawling restriction, which may limit search visibility. 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 56 characters, within a common display range. A meta description is present, with 149 characters.

Hosting and Email

DNSCloudflare
HostingCloudflare
EmailGoogle Workspace
Location Location unknown 104.20.47.133

User reviews (0)

  • No reviews yet.

Pages, Search and Sharing

Meta descriptionPubPeer enables scientists to search for their publications or their peers publications and provide feedback and/or start a conversation anonymously.
Canonical URLNot detected
LanguageEnglish (default)
Twitter CardNot detected

Unknown

gptbot 0 allowed · 1 disallowed
  • Disallow/
claudebot 0 allowed · 1 disallowed
  • Disallow/
petalbot 0 allowed · 1 disallowed
  • Disallow/
bytespider 0 allowed · 1 disallowed
  • Disallow/
ahrefsbot 0 allowed · 1 disallowed
  • Disallow/
semrushbot 0 allowed · 1 disallowed
  • Disallow/
dotbot 0 allowed · 1 disallowed
  • Disallow/
mj12bot 0 allowed · 1 disallowed
  • Disallow/
bingbot 0 allowed · 1 disallowed
  • Disallow/search
googlebot 0 allowed · 1 disallowed
  • Disallow/search
All bots 0 allowed · 1 disallowed
  • Disallow/search
  • IntervalCrawl delay 10 seconds

No sitemaps found

Registration details RDAP / WHOIS

RegistrarSquarespace Domains II LLC
Registered2012-05-19
Expires2027-05-19
Domain statusclient delete prohibited、client transfer prohibited
Nameserversigor.ns.cloudflare.com、olivia.ns.cloudflare.com
DNSSECunsigned

DNS records

TypeNameValueTTLPriority
Apubpeer.com104.20.47.133300
Apubpeer.com172.66.149.18300
AAAApubpeer.com2606:4700:10::6814:2f85300
AAAApubpeer.com2606:4700:10::ac42:9512300
MXpubpeer.comaspmx.l.google.com3001
MXpubpeer.comalt1.aspmx.l.google.com3005
MXpubpeer.comalt2.aspmx.l.google.com3005
MXpubpeer.comalt3.aspmx.l.google.com30010
MXpubpeer.comalt4.aspmx.l.google.com30010
NSpubpeer.comigor.ns.cloudflare.com86400
NSpubpeer.comolivia.ns.cloudflare.com86400
TXTpubpeer.comv=spf1 include:_spf.google.com ~all300
CAApubpeer.com0 issue "comodoca.com"3600
CAApubpeer.com0 issue "digicert.com; cansignhttpexchanges=yes"3600
CAApubpeer.com0 issue "letsencrypt.org"3600
CAApubpeer.com0 issue "pki.goog; cansignhttpexchanges=yes"3600
CAApubpeer.com0 issue "ssl.com"3600
CAApubpeer.com0 issuewild "comodoca.com"3600
CAApubpeer.com0 issuewild "digicert.com; cansignhttpexchanges=yes"3600
CAApubpeer.com0 issuewild "letsencrypt.org"3600
CAApubpeer.com0 issuewild "pki.goog; cansignhttpexchanges=yes"3600
CAApubpeer.com0 issuewild "ssl.com"3600

TLS and certificates

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectpubpeer.com
IssuerLet's Encrypt
Valid until2026-12-14T16:30 · Remaining when checked: 84 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HeaderValue
content-typetext/html; charset=UTF-8
cache-controlno-cache, private
servercloudflare
access-control-allow-origin*
set-cookieRedacted

Identified technologies

Google AnalyticsCloudflare

Recent Updates

  • Website images
  • Screenshots
  • Network details
  • Website Technologies
  • Pages and Search Information
  • HTTP Response Information
  • TLS and certificates
  • DNS Information
  • Domain Registration
  • Website profile
  • Website Description
  • Website Name
  • Website profile
  • Website Description
  • Website Name