Skip to content
https://upi.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
7 PASS 2 REVIEW
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.upi.com/
200https://upi.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://upi.com/ https://upi.com/

Consistent

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

Certificate validity

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

Recommended actions

  • 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
2 A records, 7 ms lookup
PASS
2 A records, 7 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.18.10, 104.18.19.10
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:130a, 2606:4700::6812:120a
Info::
2 nameserver(s) configured
Got: anna.ns.cloudflare.com, cash.ns.cloudflare.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: 7 ms
Got: 7 ms
A104.18.18.10, 104.18.19.10
AAAA2606:4700::6812:130a, 2606:4700::6812:120a
CNAME
NSanna.ns.cloudflare.com, cash.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
fastly-domain-validation-JIUPgvfubnnUtes-2021-09-21
google-site-verification=vnkcuJA1Q89cLmy4OZpuQKOf5Jf6ny_RVh7BpxZ11a0
SPF v=spf1 ip4:34.198.200.13 ip4:100.26.178.142 include:_spf.google.com include:spf....
CAALookup not available with standard resolver
Resolved in 7 ms

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), 71 ms total
PASS
1 redirect(s), 71 ms total
Info::
Single redirect
Got: https://upi.com → https://www.upi.com/ (301)
Info::
WWW normalization redirect

https://upi.com

26 ms · HTTP/1.1

301

https://www.upi.com/

46 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://upi.com30126 msHTTP/1.1cloudflare
2https://www.upi.com/20046 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6812:130a, 2606:4700::6812:120a
Got: 2 ms connect
IPv6 Ready
AAAA Records 2606:4700::6812:130a, 2606:4700::6812:120a Connection Reachable (2 ms)
A+
Crawlability
robots.txt present, sitemap with 500 URLs
PASS
robots.txt present, sitemap with 500 URLs
Info::
robots.txt is present
Got: 540 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 500 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 540 B Sitemaps referenced 0 User-agents Bytespider, ClaudeBot, GPTBot, *, AmazonAdBot, Applebot-Extended, CCBot, Google-Extended, meta-externalagent Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /sponsors/
Disallow: /photo-request/
Disallow: /photo_request/
Disallow: /account/
Disallow: /archive/search
Disallow: /story/stat/
Disallow: /topics/lms/
Disallow: /search
Disallow: /nl/
Disallow: /upi/dw/m/

User-agent: AmazonAdBot
Allow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: meta-externalagent
Disallow: /



A+
Domain Intelligence
upi.com — via NameCheap, Inc., 31 years, 5 months old
PASS
upi.com — via NameCheap, Inc., 31 years, 5 months old
Info::
Domain registered until Apr 20, 2027 (1 years 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: NameCheap, 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

308 days

April 20, 2027

SSL certificate

63 days

Issued by Google Trust Services

Domain age

31 years, 5 months

Registered April 19, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6812:120a

Registrar

NameCheap, Inc.

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 NameCheap, Inc.
Created April 19, 1995 (31 years, 5 months ago)
Expires April 20, 2027 (1 years)
Last Updated March 21, 2026
Name Servers anna.ns.cloudflare.com, cash.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700::6812:120a
Data source: rdap (0.1s)

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 28 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.
8 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
28 ms
Total Time Total request time from DNS lookup through full response.
28 ms

Connection waterfall

DNS Lookup 6 ms TCP Connect 2 ms TLS Handshake 8 ms Server Processing 12 ms Content Transfer 0 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Site is served via Cloudflare CDN (edge: EWR)
Got: cf-ray: 9eff2f9f8d8aefa5-EWR
Info::
CDN cache status: HIT
CDN Detected: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: 9eff2f9f8d8aefa5-EWR
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback