Skip to content
https://vine.co

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
4
PASS
3
INFO
1
Probed from Madrid, Spain
200 OK
Checks
9
3 PASS 4 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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 88 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 88 B Sitemaps referenced 0 User-agents *, bingbot Blocking No — crawling allowed
# http://www.robotstxt.org
User-agent: *
Disallow:

User-agent: bingbot
Crawl-delay: 10
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.vine.co/
200https://vine.co/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://vine.co/ → https://vine.co:443/

Consistent

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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, 37 ms lookup
PASS
2 A records, 37 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 34.208.188.129, 54.203.135.110
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-2008.awsdns-59.co.uk, ns-326.awsdns-40.com, ns-686.awsdns-21.net, ns-1085.awsdns-07.org
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::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 37 ms
Got: 37 ms
A34.208.188.129, 54.203.135.110
AAAA—
CNAME—
NSns-2008.awsdns-59.co.uk, ns-326.awsdns-40.com, ns-686.awsdns-21.net, ns-1085.awsdns-07.org
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
20 alt2.aspmx.l.google.com
30 aspmx2.googlemail.com
30 aspmx3.googlemail.com
TXT
szx8zgqr7z21hl52tn15k2crj3jb0zp3
_rfdyhtedqy5qg5y9hggyt1hw6jv92sz
xvbl4tx5lcwqgq09rr064s5vbmq6l651
e1f309c26fa846978a92ccebb75c7833
CAALookup not available with standard resolver
Resolved in 37 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.

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://vine.co

https://vine.co

717 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://vine.co200717 msHTTP/1.1
A
HTTP Probe Timing
Total 741 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
29 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
174 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
349 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
741 ms
Total Time Total request time from DNS lookup through full response.
741 ms

Connection waterfall

DNS Lookup 29 ms TCP Connect 174 ms TLS Handshake 349 ms Server Processing 189 ms Content Transfer 0 ms
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback