Skip to content
https://phys.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from New York, United Stated
200 OK
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
Domain Intelligence
phys.org — via GoDaddy.com, LLC, 24 years, 4 months old
REVIEW
phys.org — via GoDaddy.com, LLC, 24 years, 4 months old
Critical::
Domain expires in 4 days
This domain expires on April 26, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.
Got: Expires Apr 26, 2026
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: GoDaddy.com, LLC
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

EXPIRED

April 26, 2026

SSL certificate

250 days

Issued by Sectigo Limited

Domain age

24 years, 4 months

Registered April 26, 2002

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2001:48c8:17:1::55

Registrar

GoDaddy.com, LLC

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created April 26, 2002 (24 years, 4 months ago)
Expires April 26, 2026 (4 days)
Last Updated June 10, 2025
Name Servers gns1.cloudns.net, gns2.cloudns.net, gns3.cloudns.net, gns4.cloudns.net
DNSSEC Not enabled
Hosting
IP Address 2001:48c8:17:1::55
Data source: rdap (0.3s)

This domain expires on April 26, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

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

Certificate validity

250
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, 30 ms lookup
PASS
1 A records, 30 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 72.251.236.55
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: 2001:48c8:17:1::55
Info::
4 nameserver(s) configured
Got: gns4.cloudns.net, gns2.cloudns.net, gns3.cloudns.net, gns1.cloudns.net
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::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 30 ms
Got: 30 ms
A72.251.236.55
AAAA2001:48c8:17:1::55
CNAME—
NSgns4.cloudns.net, gns2.cloudns.net, gns3.cloudns.net, gns1.cloudns.net
MX
10 mx.physorg.com
TXT
facebook-domain-verification=ny8y6204en9enlmt6n8s7rlg7lkey9
google-site-verification=Ney6Zb1BPHav4nonSSwquiBBs0r0BIsEeQp5NqIxRkU
CAALookup not available with standard resolver
Resolved in 30 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://phys.org

https://phys.org

59 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://phys.org20059 msHTTP/1.1Apache
A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2001:48c8:17:1::55
Got: 2 ms connect
IPv6 Ready
AAAA Records 2001:48c8:17:1::55 Connection Reachable (2 ms)
A+
Crawlability
robots.txt present, sitemap with 49 URLs
PASS
robots.txt present, sitemap with 49 URLs
Info::
robots.txt is present
Got: 1146 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 49 entries
Info::
Sitemap index with 49 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1146 B Sitemaps referenced 1 User-agents AhrefsBot, Bytespider, Applebot-Extended, ChatGLM-Spider, ClaudeBot, GPTBot, CCbot, ImagesiftBot, *, cohere-ai, Google-Extended, FriendlyCrawler, FacebookBot, Scrapy, DataForSeoBot Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /search/
Disallow: /rss-feed/search/
Disallow: /rss-feed/breaking/search/
Disallow: /rss-feed/tags/
Disallow: /*/sort/

User-Agent: ClaudeBot
Disallow: /news/
Disallow: /partners/
Disallow: /journals/
Disallow: /tags/

User-Agent: GPTBot
Disallow: /news/
Disallow: /partners/
Disallow: /journals/
Disallow: /tags/

User-agent: FacebookBot
Disallow: /news/
Disallow: /partners/
Disallow: /journals/
Disallow: /tags/

User-agent: AhrefsBot
Disallow: /tags/

User-agent: CCbot
Disallow: /news/
Disallow: /partners/
Disallow: /journals/
Disallow: /tags/

User-Agent: Bytespider
Disallow: /news/
Disallow: /partners/
Disallow: /journals/
Disallow: /tags/

User-Agent: cohere-ai
Disallow: /news/
Disallow: /partners/
Disallow: /journals/
Disallow: /tags/

User-agent: Google-Extended
Disallow: /news/
Disallow: /tags/

User-agent: Applebot-Extended
Disallow: /news/
Disallow: /tags/

User-Agent: FriendlyCrawler
Disallow: /

User-Agent: ChatGLM-Spider
Disallow: /

User-Agent: Scrapy
Disallow: /

User-agent: DataForSeoBot
Disallow: /

User-Agent: ImagesiftBot
Disallow: /news/

Sitemap: https://phys.org/sitemap/indx/
sitemap.xml 200 OK
Type Sitemap Index URLs 49 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.phys.org/
200https://phys.org/

HTTP → HTTPS

301http://phys.org/ → https://phys.org/

Consistent

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

Connection waterfall

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

Send Feedback