Skip to content
https://php.net

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 2 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.php.net/
200https://php.net/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://php.net/ https://php.net/

Consistent

B
TLS Certificate Expiry & Recommendations
35 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

35
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 39 ms lookup
PASS
1 A records, 39 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 185.85.0.29
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a02:cb40:200::1ad
Info::
4 nameserver(s) configured
Got: dns1.easydns.com, dns3.easydns.org, dns2.easydns.net, dns4.easydns.info
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 39 ms
Got: 39 ms
A185.85.0.29
AAAA2a02:cb40:200::1ad
CNAME
NSdns1.easydns.com, dns3.easydns.org, dns2.easydns.net, dns4.easydns.info
MX
0 php-smtp4-ip4.php.net
TXT
google-site-verification=O6K8miDfoyFI4IjIQ13207kl978tUNg1HYv3G-bLabo
SPF v=spf1 ip4:140.211.15.143 ip4:45.112.84.5 ip4:142.93.197.176 ip6:2604:a880:400:d...
CAALookup not available with standard resolver
Resolved in 39 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 219 ms total
PASS
1 redirect(s), 219 ms total
Info::
Single redirect
Got: https://php.net → https://www.php.net/ (301)
Info::
WWW normalization redirect

https://php.net

94 ms · HTTP/1.1

301

https://www.php.net/

125 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://php.net30194 msHTTP/1.1myracloud
2https://www.php.net/200125 msHTTP/1.1myracloud

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (30 ms)
PASS
IPv6 reachable (30 ms)
Info::
IPv6 is configured and reachable at 2a02:cb40:200::1ad
Got: 30 ms connect
IPv6 Ready
AAAA Records 2a02:cb40:200::1ad Connection Reachable (30 ms)
A+
Crawlability
robots.txt present, sitemap with 39 URLs
PASS
robots.txt present, sitemap with 39 URLs
Info::
robots.txt is present
Got: 292 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 39 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 292 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /backend/
Disallow: /distributions/
Disallow: /stats/
Disallow: /server-status/
Disallow: /search.php
Disallow: /mod.php
Disallow: /manual/add-note.php
Disallow: /manual/vote-note.php

Disallow: /harming/humans
Disallow: /ignoring/human/orders
Disallow: /harm/to/self

A+
Domain Intelligence
php.net — via Tucows Domains Inc., 28 years, 9 months old
PASS
php.net — via Tucows Domains Inc., 28 years, 9 months old
Info::
Domain registered until Nov 17, 2029 (3 years, 7 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Tucows Domains Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Domain expiry

1223 days

November 17, 2029

SSL certificate

35 days

Issued by Let's Encrypt

Domain age

28 years, 9 months

Registered November 18, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:cb40:200::1ad

Registrar

Tucows Domains Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Tucows Domains Inc.
Created November 18, 1997 (28 years, 9 months ago)
Expires November 17, 2029 (3 years, 7 months)
Last Updated November 8, 2024
Name Servers dns1.easydns.com, dns2.easydns.net, dns3.easydns.org, dns4.easydns.info
DNSSEC Not enabled
Hosting
IP Address 2a02:cb40:200::1ad
Data source: rdap (0.2s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 120 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
27 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
30 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
33 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
121 ms
Total Time Total request time from DNS lookup through full response.
121 ms

Connection waterfall

DNS Lookup 27 ms TCP Connect 30 ms TLS Handshake 33 ms Server Processing 30 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback