Skip to content
https://uproxx.com

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
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.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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, 82 ms lookup
PASS
1 A records, 82 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 192.0.66.54
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns2.wordpress.com, ns1.wordpress.com, ns3.wordpress.com
Info::
5 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: 82 ms
Got: 82 ms
A192.0.66.54
AAAA—
CNAME—
NSns2.wordpress.com, ns1.wordpress.com, ns3.wordpress.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
specops-verification-code=73bbe4d6-a866-4888-a7c1-c8f37f01d89c
a31m3cjq281kvmj5lmempbch4q
google-site-verification=NDlQyALoODAv0r40Qsysi_MQMEwvl_LTEWJW8bIjM8E
box-domain-verification=fb68e7bfb397b481d549eed2845baf5b0abff0505ca982c9b5544696...
MS=ms90280801
google-site-verification=bOv51XfmqMl8yYjOOaxDx0aJ_HiHHsKjyYFyOlIPuso
anthropic-domain-verification-ex6jap=AkAzFZJ6kobPEwETMH7OdMXO0
adobe-idp-site-verification=528bb201a5d7810853f60ff265fffbd4d9f8a0e6fcc52b7a0e58...
facebook-domain-verification=xrsxdbbofqfecekjge409rx4w3bebp
SPF v=spf1 include:_spf.google.com include:spfa.cpmails.com ~all
google-site-verification=9xsv5g-oIxai2uK1YENCbvbMP_rVMDtW-fSk2uzScWQ
linkedin-site-verification=aa362438-434d-462d-b58a-0dcff8c70de1
google-site-verification=Zw8NkIuM77MtM_r_Do4w9vJnbR1U_5Ru7UPCwuwNcDw
google-site-verification=Gky1Dh2PQrsuKi7htd8ap13H1P-EEevVtIwy0meLkbM
google-site-verification=mAPnwEvQRG7er4XXhhz8sru1u5V17rcrJUMZ9RBqe2I
google-site-verification=mAPnwEvQRG7er4XXhhz8sru1u5V17rcrJUMZ
google-site-verification=OPKessHHAV6eHKWnu2Jf4sPmdZFuTjPXd-DovxrrKGs
CAALookup not available with standard resolver
Resolved in 82 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://uproxx.com

https://uproxx.com

6 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://uproxx.com2006 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 2656 URLs
PASS
robots.txt present, sitemap with 2656 URLs
Info::
robots.txt is present
Got: 308 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2656 entries
Info::
Sitemap index with 2656 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 308 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# Uproxx Start
User-agent: *
Disallow: /hidden/
Disallow: /ksk/
Disallow: /media/
Disallow: /smokingsection/
Disallow: /uncategorized/
Disallow: /up/
Disallow: /videos/
# Uproxx End
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
# Sitemap archive
Sitemap: https://uproxx.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 2656 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::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.uproxx.com/
200https://uproxx.com/

Preferred variant: non-www

HTTP → HTTPS

301http://uproxx.com/ → https://uproxx.com/

Consistent

A+
Domain Intelligence
uproxx.com — via GoDaddy.com, LLC, 19 years, 9 months old, hosted on WordPress.com (Automattic)
PASS
uproxx.com — via GoDaddy.com, LLC, 19 years, 9 months old, hosted on WordPress.com (Automattic)
Info::
Domain registered until Nov 17, 2030 (4 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: 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.
Info::
Hosting: WordPress.com (Automattic)
Got: AS2635
Domain expiry

1618 days

November 17, 2030

SSL certificate

46 days

Issued by Let's Encrypt

Domain age

19 years, 9 months

Registered November 1, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.66.54

Registrar

GoDaddy.com, LLC

Unlocked 2 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 GoDaddy.com, LLC
Created November 1, 2006 (19 years, 9 months ago)
Expires November 17, 2030 (4 years, 7 months)
Last Updated May 17, 2024
Name Servers ns1.wordpress.com, ns2.wordpress.com
DNSSEC Not enabled
Hosting
IP Address 192.0.66.54
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
Data source: rdap (0.3s)

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 50 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
45 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
49 ms
Total Time Total request time from DNS lookup through full response.
51 ms

Connection waterfall

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

Send Feedback