wordpress.org

Last analyzed: Refreshing...

Looks Normal

Standard signals observed

This reflects observed technical signals, not a judgment of the website's intent or safety. Wondering if WordPress is legit? Below you'll find technical signals for wordpress.org including domain age, HTTPS security, DNS records, and redirect behavior to help you decide if this website is trustworthy.

Observed signals
Domain registered 22 years ago
Valid HTTPS certificate
DNS records present
1 redirect observed
Favicon detected
HSTS enabled
AI Summary Plain-language explanation of the signals

The domain wordpress.org hosts an active website with DNS records resolving to the IP address 198.143.164.252 and using nameservers such as ns1.wordpress.org and ns4.wordpress.org. Registered through MarkMonitor Inc. and established over 22 years ago, the domain’s registration extends until March 28, 2035. The site enforces HTTPS with a valid wildcard certificate issued by Let's Encrypt, expiring in February 2026. The website redirects HTTP traffic to HTTPS and appears to be built using WordPress technology. These signals describe technical characteristics only and do not indicate intent or safety.

HTTP Response
HTTPS 1 redirect

Final URL:

https://wordpress.org/
Redirect chain
301 http://wordpress.org/ https://wordpress.org/
200 https://wordpress.org/
TLS Certificate
Valid
Yes
Covers Domain
Yes
Type
Wildcard

Expires in 86 days

Certificate details

Subject: /CN=wordpress.org

Issuer: /C=US/O=Let's Encrypt/CN=E8

Chain: 2 certificates

Subject Alt Names (2)
*.wordpress.org
wordpress.org matches
DNS Records
A Records
1
AAAA
1
NS
4
IP addresses & nameservers

A: 198.143.164.252

AAAA: 2607:f978:5:8002::c68f:a4fc

NS: ns3.wordpress.org, ns2.wordpress.org, ns4.wordpress.org, ns1.wordpress.org

MX records (1)
mail.wordpress.org
TXT records (3)
google-site-verification=UL0sGJ1dZbCT4J7pGrLW3hqM_I1LJ8pU...
google-site-verification=t8FjG1vzC4OFZJ8qL4SkR8xxtLyKldXK...
v=spf1 ip4:66.155.40.0/24 ip4:198.143.164.0/24 include:he...
Domain Registration
22 years old
Registered Mar 28, 2003
Registrar MarkMonitor Inc.
Expires Mar 28, 2035
More details

Last changed: Jul 06, 2025

Status: client delete prohibited client transfer prohibited client update prohibited

Nameservers: ns1.wordpress.org, ns2.wordpress.org, ...

Robots.txt (Crawl directives)
Status
200 OK
Crawl Access
Allowed (with restrictions)

These directives apply to crawlers requesting this host.

Agents
1
Rules
7
Sitemaps
9
Directive breakdown
Disallow 4
Allow 3
Sitemaps 9
Sitemap URLs
https://wordpress.org/sitemap.xml
https://wordpress.org/news-sitemap.xml
https://wordpress.org/themes/sitemap.xml
https://wordpress.org/plugins/sitemap.xml
https://wordpress.org/news/sitemap.xml

+ 4 more

Raw content
Sitemap: https://wordpress.org/sitemap.xml
Sitemap: https://wordpress.org/news-sitemap.xml
Sitemap: https://wordpress.org/themes/sitemap.xml
Sitemap: https://wordpress.org/plugins/sitemap.xml
Sitemap: https://wordpress.org/news/sitemap.xml
Sitemap: https://wordpress.org/showcase/sitemap.xml
Sitemap: https://wordpress.org/documentation/sitemap.xml
Sitemap: https://wordpress.org/patterns/sitemap.xml
Sitemap: https://wordpress.org/photos/sitemap.xml
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Allow: /wp-admin/load-scripts.php
Allow: /wp-admin/load-styles.php

User-agent: *
Disallow: /search
Disallow: /?s=

User-agent: *
Disallow: /plugins/search/

Robots.txt directives are advisory instructions for crawlers and do not enforce access control.

Tech Stack
Platform
WordPress (medium)
JS Framework
Not detected
Server
nginx
CDN
Not detected
Analytics
1
Security Headers
2 / 6
nginx Google Tag Manager
HSTS X-Frame-Options
Detection evidence
HSTS:
strict-transport-security header present
nginx:
server header: 'nginx'
WordPress:
WordPress content paths detected
X-Frame-Options:
x-frame-options header present
Google Tag Manager:
Google Tag Manager container found

Technologies detected from HTTP headers and HTML patterns. Detection is passive and may not capture all technologies.