Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BRedirect Chain2 redirect(s), 246 ms totalREVIEW
https://tinypic.com
68 ms · HTTP/1.1
https://tinypic.com/tinypic-blog/
100 ms · HTTP/1.1
https://tinypic.com/tinypic-blog
78 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://tinypic.com | 301 | 68 ms | HTTP/1.1 | cloudflare |
| 2 | https://tinypic.com/tinypic-blog/ | 301 | 100 ms | HTTP/1.1 | cloudflare |
| 3 | https://tinypic.com/tinypic-blog | 200 | 78 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations61 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
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 Records2 A records, 39 ms lookupPASS
| A | 199.60.103.185, 199.60.103.85 |
| AAAA | — |
| CNAME | — |
| NS | ns-1900.awsdns-45.co.uk, ns-1433.awsdns-51.org, ns-642.awsdns-16.net, ns-378.awsdns-47.com |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| TXT | google-site-verification=5y_XYqwXMCyJwSNEwHNq6bqYGZ2_0WjLXygrIPpkG4M google-site-verification=W9qsUl2KEvzczwcJvxTfkWmCxWPpRqsWW4ysuu2UxpM SPF v=spf1 mx ip4:66.11.51.0/24 ip4:66.11.55.0/24 include:_spf.google.com ~all |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+Crawlabilityrobots.txt present, sitemap with 26 URLsPASS
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: *
Disallow: /_hcms/preview/
Disallow: /hs/manage-preferences/
Disallow: /hs/preferences-center/
Disallow: /*?*hs_preview=*
Disallow: /*?*hsCacheBuster=*
- https://tinypic.com/tinypic-blog/understanding-digital-storage-a-comprehensive-guide-to-data-measurement-units
- https://21595784.fs1.hubspotusercontent-na1.net/hubfs/21595784/Logo_Gradient_Horizontal.png
- https://21595784.fs1.hubspotusercontent-na1.net/hubfs/21595784/Brand%20-%20Logos%2c%20fonts%2c%20and%20brand-related%20resources/2023/Assets/Facebook_Dark-1.png
- https://21595784.fs1.hubspotusercontent-na1.net/hubfs/21595784/Brand%20-%20Logos%2c%20fonts%2c%20and%20brand-related%20resources/2023/Assets/Pinterest_Dark.png
- https://21595784.fs1.hubspotusercontent-na1.net/hubfs/21595784/X_icon.png
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencetinypic.com — via Amazon Registrar, Inc., 22 years, 3 months old, hosted on CloudflarePASS
313 days
April 25, 2027
61 days
Issued by Google Trust Services
22 years, 3 months
Registered April 25, 2004
Not enabled
Protects against DNS spoofing
Cloudflare
ASN AS209242
199.60.103.85
Amazon Registrar, Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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