What is this website?
wordpress.org is currently classified in the Software category based on observed public pages. An About page was also found. Recurring page-metadata topics include orgwordpress orgwordpress orgwordpress, newswordpress orgwordpress orgwordpress, wordcamp.
No listed local patterns observedHomepage-only analysis is not a malware clearance. Read the scope and findings below.
How to read this report
Safety Score evaluates observed signals. Evidence Confidence measures how complete, direct, fresh, and consistent those signals are.
No automated scan can guarantee that a website is safe.
Independent evidence brief
What we observed about wordpress.org
The latest scan examined 10 public pages on wordpress.org. Website descriptions below come from the site itself. Registration, connection and threat findings were checked separately.
Purpose and visible content
On its About page, the site says: our mission: democratize publishing the freedom to build. the freedom to change. the freedom to share. our story WordPress started in 2003 when Mike…
- About – WordPress.orgWordPress.orgWordPress.orgWordPress.orgWordPress.orgour mission: democratize publishing the freedom to build. the freedom to change. the freedom to share. our story…
- Privacy – WordPress.orgWordPress.orgWordPress.orgWordPress.orgWordPress.orgPrivacy policy WordPress.org websites (collectively “WordPress.org” in this document) refer to sites hosted on the WordPress.org, WordPress.net, WordCamp.org,…
Registrar and domain history
Registered on Mar 28, 2003. Registrar: MarkMonitor Inc..
Recorded expiry date: Mar 28, 2035. Registry data can change.
Connection and hosting evidence
The checked homepage returned HTTP 200 in about 1000 ms.
A valid TLS certificate was observed, expiring Dec 22, 2026.
Threat checks and score context
External malware-provider coverage was unavailable. The report does not treat this missing check as a clean result.
Safety Score: 75/100. Evidence Confidence: 70%. These measure different things.
Public content profile
Pages reviewed on wordpress.org
We sampled public pages from this website to understand its subject and contact paths. The titles and short descriptions below come from the website itself. They are not endorsements or independent safety findings.
Public page evidence
Topics and keywords observed on wordpress.org
These phrases were extracted locally from sampled public page metadata. They are observations, not search-volume or ranking estimates.
At a glance
Key findings
Report is current
The displayed evidence comes from the published immutable scan.
Confidence is separate
Unavailable evidence is shown as missing and never counted as clean.
Verify before sensitive actions
Check the exact URL and context before payments, credentials, or downloads.
Fully explainable
Why this score?
Threat providers were unavailable. The neutral uncertainty baseline is not a clean verdict.
Domain registration age and expiry were checked.
Observed DNS records and network address were checked.
Observed certificate validity and TLS protocol were checked.
Observed security header values were checked for basic protective settings. Empty values, disabled HSTS and unrecognized values receive no credit. This is not a complete browser-policy validation.
Observed site metadata and About page were checked. Publisher-supplied details are not independently verified.
Popularity is weak context, not proof of safety. Unranked sites use a neutral baseline.
Observed HTTP status and final connection scheme were checked.
Server-side analysis
Automated security checks
Homepage HTML only · Eight local rule families · local-security-v1
Checks use the fetched page and redirect chain. Scripts are not executed, forms are not submitted, and linked files are not downloaded. This is not a malware clearance.
No listed local patterns observed. The limited rule set cannot detect every threat or behavior.
External threat intelligence
Local checks do not query external reputation databases. An unavailable check is never a clean result.
Registration
Domain information
Infrastructure
Network & hosting
At a glance
Infrastructure summary
A compact view of the connection, DNS and security surface. These observations describe what the scanner could verify at scan time and do not prove ownership or ongoing availability.
Page telemetry
Observed page statistics
These counters describe the fetched response and sampled HTML. Script counts describe references in the markup, not a complete browser network log. Cookie counts cover observed response headers.
Encrypted transport
TLS certificate
Resolution
DNS footprint
DNSKEY presence does not verify the DNSSEC signature chain. Missing records can mean no record was returned or the lookup was unavailable.
66.6.42.252TTL —2620:109:b00a::4206:2afcTTL —ns1.wordpress.orgTTL —ns2.wordpress.orgTTL —ns3.wordpress.orgTTL —ns4.wordpress.orgTTL —10 smtp1-dca.wordpress.orgTTL —10 smtp2-dca.wordpress.orgTTL —0 iodef "mailto:caa@wordpress.org"TTL —0 issue "letsencrypt.org;validationmethods=dns-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/53691143"TTL —google-site-verification=t8FjG1vzC4OFZJ8qL4SkR8xxtLyKldXKbswyeemQS5wTTL —google-site-verification=UL0sGJ1dZbCT4J7pGrLW3hqM_I1LJ8pUi2WBEI_98kITTL —v=spf1 ip4:66.6.42.0/24 ip4:66.155.40.0/24 include:helpscoutemail.com -allTTL —Responsible disclosure
security.txt
No readable security.txt file was observed at the standard locations. This is informational and is not evidence of malware.
Browser protections
Security headers
Response headers
Cookie protections
No Set-Cookie header was observed on the sampled homepage response. Other pages may set cookies separately.
Detected stack
Technologies
Versions are shown only when publicly exposed by the page or response headers. An observed version is not, by itself, proof of a vulnerability.
JavaScript library advisories
JavaScript advisory analysis was not recorded for this scan.
Recommended maintenance checks
About this website
What the site says about itself
our mission: democratize publishing the freedom to build. the freedom to change. the freedom to share. our story WordPress started in 2003 when Mike Little and Matt Mullenweg created a fork of b2/cafelog. The need for an elegant, well-architected personal publishing system was clear even then. Today, WordPress is built on PHP and MariaDB, and licensed…
This is publisher supplied information. The independent safety findings are shown separately.
Publisher supplied
Social profiles observed on this website
These links appeared on the website. We have not independently verified ownership of the linked accounts.
X
Facebook
Instagram
LinkedIn
TikTok
X
GitHub
X
Publisher supplied
Public contact details
These details were observed on the website, not independently verified as an active support channel.
Structured facts
Website identity & response
Connection path
Redirect chain
No redirect hop was recorded for the sampled homepage.
Compared with the previous scan
What changed
This comparison uses persisted scan evidence only. A changed signal can reflect a real website change, a different response or newly available evidence.
Explainable matching
Digital fingerprint
Comparable components help find technically related websites. A match does not prove common ownership.
Material changes only
Change history
No meaningful changes recorded yet.
Visual evidence
Website screenshot
For site owners
Show your verified trust report
Place this lightweight badge in your footer to show visitors an independent, dated WebsiteVirusScanner report. It can increase visitor confidence, but it never changes or guarantees the score.
Use the current report link so visitors can verify the evidence. A badge is a transparency signal, not a paid ranking boost.
Questions about wordpress.org
FAQ
Is wordpress.org safe to visit?
The latest Safety Score is 75/100 with 70% Evidence Confidence. This is a point-in-time assessment of observed technical signals, not a guarantee. Check the exact address and avoid entering payment details if anything looks unusual.
Did the scan detect malware on wordpress.org?
External threat-provider coverage was unavailable for this scan, so malware status is unverified.
When was wordpress.org registered?
The public registry record shows Mar 28, 2003. Registration details may be privacy-protected or updated later.
Did wordpress.org have a valid TLS certificate?
The scanner observed a valid TLS certificate using TLSv1.3. A valid certificate alone does not establish that the site is safe.
How does wordpress.org describe itself?
The website's About page describes its purpose in the report above. This is publisher-supplied information and is separate from independent security findings.
Can a paid listing change this website's score?
No. Premium placement and owner-supplied pages are labelled separately. Technical evidence, the Safety Score and moderation decisions remain independent.