Show

T.co t.co / Twitter

Need help with your SEO?
Online Status
Online

Server IP address resolved: Yes
Http response code: 200
Response time: 0.07 sec.
Last Checked: 02/27/2019

T.co receives about eight million unique visitors and twenty million pageviews per day. The estimated value of t.co is two hundred million USD. Each unique visitor makes about 2.2 pageviews on average.

Over the time t.co has been ranked as high as 22 in the world, while most of its traffic comes from United States, where it reached as high as 24 position.

It’s good for t.co that their server is also located in United States, as that enables the majority of their visitors to benefit from a much faster page load time.

At the time of the last check (January 28, 2019) t.co has a valid and up-to-date SSL certificate that expires on November 05, 2019.

According to Google Safe Browsing, Google Safe Search, Symantec and Web of Trust t.co is quite a safe domain.

Mobile-Friendly test indicates that t.co is well optimized for mobile and tablet devices.

Global Rank
39
Average Load Time
0.59sec
Links In Count
96,046
Website Value
$234.5 M
Overview
Last Updated: 06/18/2019
Overall result - "t.co" is SAFE.
We gather website safety and reputation data and compare it with available third-party sources so we calculate own safety and trustworthiness rate based on information that we get.
Norton Connect Safe
Last Updated: 01/12/2019
NCS "t.co" OK.

Norton ConnectSafe evaluates t.co for any unsafe and insecure content. The results are critical for families with young children.

Google Safe Search
Last Updated: 10/10/2016
GSS "t.co" OK.

SafeSearch is used as a parental control tool to filter out any inappropriate for your children search results on your devices: phones, tablets or personal computers.

Google Safe Browsing
Last Updated: 02/18/2019
Malware not found at "t.co".
"t.co" is not a phishing page.
"t.co" does not install unwanted software.
"t.co" does not contain harmfull applications.
Google Safe Browsing notifies when websites are compromised by malicious actors. These protections work across Google products and provide a safer online experience.
Site Advisor
Last Updated: 01/09/2019
SA "t.co" OK.

McAfee assesses t.co for a meaningful set of security threats. Featured dangers from annoying pop-ups to hidden Trojans, that can steal your identity, will be revealed. McAfee does not analyze t.co for mature or inappropriate content, only security checks are evaluated.

Web of Trust
Last Updated: 01/09/2019
WOT "t.co" VERY GOOD.

The WOT calculates reputation of the t.co. This reputation system receives ratings from users and information from third-party sources, assesses the t.co for safety features and confirms, whether t.co is suitable for children.

SSL Information
Domain t.co
Issuer DigiCert SHA2 High Assurance Server CA
Algorithm RSA-SHA256
Valid form 10/31/2018
Expiration 11/05/2019
Signed Certificate is not self signed
Additional Domains t.co
www.t.co
Server Location
San Francisco
California
United States
ASN Information

ASN ID: 13414
ASN Title: TWITTER - Twitter Inc., US

Last Update: 05/29/2019

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/whois_reporting/index.html
#
# Copyright 1997-2018, American Registry for Internet Numbers, Ltd.
#

ASNumber: 13414
ASName: TWITTER
ASHandle: AS13414
RegDate: 2010-07-09
Updated: 2015-02-19
Ref: https://rdap.arin.net/registry/autnum/13414

OrgName: Twitter Inc.
OrgId: TWITT
Address: 1355 Market Street
Address: Suite 900
City: San Francisco
StateProv: CA
PostalCode: 94103
Country: US
RegDate: 2010-03-08
Updated: 2018-05-15
Ref: https://rdap.arin.net/registry/entity/TWITT

OrgNOCHandle: NETWO3685-ARIN
OrgNOCName: Network Operations
OrgNOCPhone: +1-415-222-9670
OrgNOCEmail: noc@twitter.com
OrgNOCRef: https://rdap.arin.net/registry/entity/NETWO3685-ARIN

OrgTechHandle: NETWO3685-ARIN
OrgTechName: Network Operations
OrgTechPhone: +1-415-222-9670
OrgTechEmail: noc@twitter.com
OrgTechRef: https://rdap.arin.net/registry/entity/NETWO3685-ARIN

OrgTechHandle: SOUTH69-ARIN
OrgTechName: Southern, Timothy
OrgTechPhone: +1-415-416-2326
OrgTechEmail: tsouthern@twitter.com
OrgTechRef: https://rdap.arin.net/registry/entity/SOUTH69-ARIN

OrgAbuseHandle: TNA33-ARIN
OrgAbuseName: Twitter Network Abuse
OrgAbusePhone: +1-415-222-9670
OrgAbuseEmail: net-abuse@twitter.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/TNA33-ARIN

OrgTechHandle: YURCH-ARIN
OrgTechName: Yurchenko, Anton
OrgTechPhone: +1-408-207-2488
OrgTechEmail: ayurchenko@twitter.com
OrgTechRef: https://rdap.arin.net/registry/entity/YURCH-ARIN

RAbuseHandle: TNA33-ARIN
RAbuseName: Twitter Network Abuse
RAbusePhone: +1-415-222-9670
RAbuseEmail: net-abuse@twitter.com
RAbuseRef: https://rdap.arin.net/registry/entity/TNA33-ARIN

RTechHandle: NETWO3685-ARIN
RTechName: Network Operations
RTechPhone: +1-415-222-9670
RTechEmail: noc@twitter.com
RTechRef: https://rdap.arin.net/registry/entity/NETWO3685-ARIN

RNOCHandle: NETWO3685-ARIN
RNOCName: Network Operations
RNOCPhone: +1-415-222-9670
RNOCEmail: noc@twitter.com
RNOCRef: https://rdap.arin.net/registry/entity/NETWO3685-ARIN

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/whois_reporting/index.html
#
# Copyright 1997-2018, American Registry for Internet Numbers, Ltd.
#

HTML Metatags
Title
t.co / Twitter
The title has an optimal length. Search engines typically displays the first 50–70 characters of a title tag. If you keep your titles under 70 characters, our research suggests that you can expect about 90% of your titles to display properly.
Description
The description is too short. If a description is too short, the search engines may add text found elsewhere on the page. Note that search engines may show a different description from the one you have authored if they feel it may be more relevant to a user's search.
Encoding
You should always specify the encoding used for an HTML page. If you don't, you risk that characters in your content are incorrectly interpreted. This is not just an issue of human readability, increasingly machines need to understand your data too.
Language
Language not found
Identifying the language of your content allows you to automatically do a number of things, from changing the look and behavior of a page, to assisting search engines in extracting information. If part of the page uses text in a different language, you can add a language attribute with a different value to the element that surrounds that content.
Language Region
Not Found
Images
Attribute ALT
Success, no any <img> without defined ALT attribute. Alt text is helpful to end users if they have images disabled or if the image does not properly load.
As a general rule, search engines do not interpret the content of image files. The text provided in the <img alt> attribute enables the site owner to provide relevant information to the search engine and to the end user.
H1-H6 Tags Information

For search engines, <H> tags helps understand the structure of the text on a page better. For users, headings are like anchors in a wall of text, navigating them through the page and making it easier to digest. The <h1> tag reinforces the core keyword(s) found in the <title>, <description>, and the <body>. We recommend that the <h1> tag includes keywords that reflect the contents of the page and that it is not longer than 150 characters in length, but don’t overuse the tags and the keywords in them. Keep it readable for users.

H1
The H1 tag is missing
Your H1 introduces the topic your page is all about, just as a title tells a reader what a book is all about. Add a header to the page by using a H1 tag and place it within the BODY of the page source.
H2
The H2s are akin to book chapters, describing the main topics you’ll cover in sections of the article.
H3
Subsequent headers, H3s to H6s, serve as additional sub-headings within each section, just as a book chapter may be split up by multiple sub-topics.
H4
H5
H6
Iframes Information
iFrame
iFrames not found.
Since search engines consider the content in iframes to belong to another website, the best you can hope for is no effect on SEO. Iframes tend to neither help nor hurt your search engine ranking. For this reason, it’s best to refrain from using iframes on main pages that you want to rank high in search engine results. Instead, fill high-priority pages with useful, unique content and save iframes for other pages.
Code To Text Ratio
Code To Text Ratio
9.21 %
A good code to text ratio is anywhere from 25 to 70 percent. This percentage refers to the visible text ratio, as opposed to HTML elements, image tags and other non-visible information. This has become especially apparent since search engines, such as Google, released the Panda update which placed importance on content-driven sites.
Favicons

Favicons are the little piece of graphic that represents your brand on browser tabs, bookmark lists, search history, search ads and even search results. These files are placed in a file called favicon.ico and placed in the root directory of a website. There are no direct SEO effects of having favicons. However, there may be indirect benefits such as increased usability of site and bookmarks. It makes your website look more professional and help a users to remember your site while browsing through multiple URLs. If you want to get mentioned benefits you have to specify icons for different web browsers and sometimes even for different mobiles.

Default Favicon
Line 5, https://abs.twimg.com/favicons/favicon.ico
Backup icon for most desktop browsers (if no icon of the right size is found). Tag format <link rel="shortcut icon" href="path-to-16x16-icon.ico" type="image/x-icon" />
16x16 Optional Favicon
Standard icon for outdated browsers or small resolution hand held devices. Tag format <link rel="icon" type="image/png" sizes="16x16" href="path-to-16x16.png">
32x32 Optional Favicon
Standard for most desktop browsers. Tag format <link rel="icon" sizes="32x32" href="path-to-32x32.png">
96x96 Optional Favicon
Mostly used as GoogleTV icon. Tag format <link rel="icon" type="image/png" sizes="96x96" href="path-to-96x96.png">
Default Apple Icon
Backup icon for apple devices (if no icon of the right size is found). Preferrable size 60x60. Tag format <link rel="apple-touch-icon" sizes="72x72" href="path-to-small-icon.png">
180x180 Apple Icon
iPhone 6 plus icons. Tag format <link rel="apple-touch-icon" sizes="180x180" href="path-to-180x180.png">
152x152 Apple Icon
iPad, iPad mini icons. Tag format <link rel="apple-touch-icon" sizes="152x152" href="path-to-icon-152x152.png">
167x167 Apple Icon
iPad Pro icon. Tag format <link rel="apple-touch-icon" sizes="167x167" href="path-to-167x167.png">
Robots.txt Information

Robots.txt is a text file that website owners can create to tell search engine bots how to crawl and index pages on their site.

Robots File
Robots File Loaded successfully (/robots.txt)
You can have multiple lines of instructions to allow or disallow specific URLs and add multiple sitemaps. If you do not disallow a URL, then search engine bots assume that they are allowed to crawl it.
Disallow
1 record(s)
Other User-Agent
1 record(s)
Default User-Agent
1 record(s)
Sitemap

A sitemap is an XML file where is provided information about each URL: when it was last updated, how often it changes, and how important it is in relation to other URLs in the site. Search engines crawling bots read this file to more efficiently and intelligently crawl your site and to find URLs that may be isolated from rest of the site's content.

Default Sitemap
Sitemap File failed Loaded (/sitemap.xml)
Your site will benefit from having a sitemap.
WHOIS

Domain Name: t.co
Registry Domain ID: D740225-CO
Registrar WHOIS Server: whois.corporatedomains.com
Registrar URL: whois.corporatedomains.com
Updated Date: 2018-04-27T05:43:56Z
Creation Date: 2010-04-26T07:50:40Z
Registry Expiry Date: 2019-04-25T23:59:59Z
Registrar: CSC Corporate Domains, Inc.
Registrar IANA ID: 299
Registrar Abuse Contact Email: domainabuse@cscglobal.com
Registrar Abuse Contact Phone: +1.8887802723
Domain Status: serverDeleteProhibited https://icann.org/epp#serverDeleteProhibited
Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
Domain Status: serverUpdateProhibited https://icann.org/epp#serverUpdateProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name:
Registrant Organization: Twitter, Inc.
Registrant Street:
Registrant Street:
Registrant Street:
Registrant City:
Registrant State/Province: CA
Registrant Postal Code:
Registrant Country: US
Registrant Phone:
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID:
Admin Name:
Admin Organization:
Admin Street:
Admin Street:
Admin Street:
Admin City:
Admin State/Province:
Admin Postal Code:
Admin Country:
Admin Phone:
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID:
Tech Name:
Tech Organization:
Tech Street:
Tech Street:
Tech Street:
Tech City:
Tech State/Province:
Tech Postal Code:
Tech Country:
Tech Phone:
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: d01-01.ns.twtrdns.net
Name Server: d01-02.ns.twtrdns.net
Name Server: r01-02.ns.twtrdns.net
Name Server: ns4.p34.dynect.net
Name Server: ns3.p34.dynect.net
Name Server: r01-01.ns.twtrdns.net
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2018-11-08T12:40:07Z

DNS Records
HostA RecordTTL
t.co104.244.42.6930
HostMX RecordPriorityTTL
HostNS RecordTTL
t.coa.r06.twtrdns.net13999
t.cob.r06.twtrdns.net13999
t.coc.r06.twtrdns.net13999
t.cod.r06.twtrdns.net13999
t.cod01-01.ns.twtrdns.net13999
t.cod01-02.ns.twtrdns.net13999
t.cons1.p34.dynect.net13999
t.cons2.p34.dynect.net13999
t.cons3.p34.dynect.net13999
t.cons4.p34.dynect.net13999
HostTXT RecordTTL
t.cov=spf1 -all293

ns1.p26.dynect.net
TTL: 293
Email address: ops\@twitter.com
Serial: 2478
Refresh: 3600
Retry: 600
Expire: 604800
Minimum: 60

Errors
Line: 1 Column: 1 - 97
"...<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html..."
Line: 36 Column: 54 - 58
"...out Us</a></li> ..."
Line: 37 Column: 61 - 65
"...ontact</a></li> ..."

Last tested: 05/28/2017

Desktop
Desktop Speed
99%
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:

http://t.co/static/images/bird.png (expiration not specified)

Desktop Resource Breakdown
Total Resources2
Number of Hosts1
Static Resources1

Last tested: 04/06/2018

Mobile
Mobile Usability
86%
Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="https://blog.twitter.com/">Blog</a> and 4 others are close to other tap targets final.

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.
The following text fragments have a small font size. Increase the font size to make them more legible.

Back to Twitter renders only 5 pixels tall (14 CSS pixels) final.
Learn more renders only 5 pixels tall (14 CSS pixels) final.
2018 Twitter and 1 others render only 4 pixels tall (11 CSS pixels) final.
About Us and 8 others render only 4 pixels tall (11 CSS pixels) final.

Mobile Speed
99%
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:

http://t.co/static/images/bird.png (expiration not specified)

Mobile Resource Breakdown
Total Resources2
Number of Hosts1
Static Resources1