Skip to content
https://tiny.cc

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
9
5 PASS 3 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
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.tiny.cc/
200https://tiny.cc/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://tiny.cc/ https://tiny.cc/

Consistent

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

Certificate validity

74
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
1 A records, 127 ms lookup
PASS
1 A records, 127 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 157.245.113.153
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: pdns1.registrar-servers.com, pdns2.registrar-servers.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: 127 ms
Got: 127 ms
A157.245.113.153
AAAA
CNAME
NSpdns1.registrar-servers.com, pdns2.registrar-servers.com
MX
10 eforward1.registrar-servers.com
10 eforward2.registrar-servers.com
10 eforward3.registrar-servers.com
15 eforward4.registrar-servers.com
20 eforward5.registrar-servers.com
TXT
SPF v=spf1 include:spf.efwd.registrar-servers.com ~all
google-site-verification=C_-q4wqr-ajSXqIIg8wSeUPCg7Hrc7VjWE8MpfJxsM8
SPF v=spf1 include:spf.efwd.registrar-servers.com include:_spf.google.com include:ma...
CAALookup not available with standard resolver
Resolved in 127 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://tiny.cc

https://tiny.cc

462 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://tiny.cc200462 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 12 URLs
PASS
robots.txt present, sitemap with 12 URLs
Info::
robots.txt is present
Got: 104 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 12 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 104 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
Sitemap: https://tiny.cc/sitemap.xml

User-agent: *
Disallow: /tiny/secureimage
Disallow: /tiny/storage

sitemap.xml 200 OK
A+
Domain Intelligence
tiny.cc — via NameCheap, Inc., 20 years, 4 months old, hosted on DigitalOcean
PASS
tiny.cc — via NameCheap, Inc., 20 years, 4 months old, hosted on DigitalOcean
Info::
Domain registered until Mar 12, 2027 (10 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: 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.
Info::
Hosting: DigitalOcean
Got: AS14061
Domain expiry

269 days

March 12, 2027

SSL certificate

74 days

Issued by Let's Encrypt

Domain age

20 years, 4 months

Registered March 12, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

DigitalOcean

ASN AS14061

157.245.113.153

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 March 12, 2006 (20 years, 4 months ago)
Expires March 12, 2027 (10 months)
Last Updated February 11, 2022
Name Servers pdns1.registrar-servers.com, pdns2.registrar-servers.com
DNSSEC Not enabled
Hosting
IP Address 157.245.113.153
ASN AS14061 (DIGITALOCEAN-ASN - DigitalOcean, LLC, US)
Provider DigitalOcean
Data source: rdap (0.7s)

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

Connection waterfall

DNS Lookup 3 ms TCP Connect 119 ms TLS Handshake 121 ms Server Processing 124 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