thiruttuvcd.me

To see this page as it is meant to appear, we ask that you please enable your Javascript! Home ThiruttuVCD Home New Movies Tamil Serials IT Tamil Vodafone launches m-pesa mobile money service ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    thiruttuvcd.me
  • Favicon
  • Alexa Rank
    #10811
  • Google Page Rank
    PR 2
  • Ip Address
    108.162.203.245
  • Page Size
    115.2 KB
  • Images
    105 GIF, 21 JPG, 1 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 25 0 0 0 0

Website Meta Analysis



  • Title
    Watch Tamil Video Online | Tamil Movie Reviews Previews Cinema News Movie Trailer Online
  • Meta Keyword
  • Meta Description
    To see this page as it is meant to appear, we ask that you please enable your Javascript! Home ThiruttuVCD Home New Movies Tamil Serials IT Tamil Vodafone launches m-pesa mobile money service in Delhi and NCR region Aircel offers free 3G service ...

Technical Analysis



  • Webserver
    cloudflare-nginx
  • Ip Address
    108.162.203.245
  • Domain Age
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from thiruttuvcd.me.

HTML Analysis

  • server: cloudflare-nginx
  • date: Thu, 22 Aug 2013 05:12:58 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • last-modified: Thu, 22 Aug 2013 04:53:41 GMT
  • expires: Thu, 22 Aug 2013 05:53:41 GMT
  • pragma: public
  • cache-control: max-age=2444, public, must-revalidate, proxy-revalidate
  • x-powered-by: W3 Total Cache/0.9.2.11
  • vary: Accept-Encoding
  • x-pingback: http://www.thiruttuvcd.me/xmlrpc.php
  • cf-ray: a1d123239f70104
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
WHOIS TERMS & CONDITIONS: Access to .ME WHOIS information is provided to
assist persons in determining the contents of a domain name registration
record in the .ME registry database. The data in this record is provided by
.ME Registry for informational purposes only, and .ME Registry does not
guarantee its accuracy. This service is intended only for query-based
access. You agree that you will use this data only for lawful purposes
and that, under no circumstances will you use this data to: (a) allow,
enable, or otherwise support the transmission by e-mail, telephone,
facsimile, or other electronic processes of mass unsolicited, commercial
advertising or solicitations to entities other than the data recipient's own
existing customers; or (b) enable high volume, automated, electronic
processes that send queries or data to the systems of Registry Operator,
except as reasonably necessary to register domain names or modify existing
registrations. All rights reserved. .ME Registry reserves the right to modify
these terms at any time. By submitting this query, you agree to abide by this
policy.

Domain ID:D3938221-ME
Domain Name:THIRUTTUVCD.ME
Domain Create Date:09-Feb-2012 21:17:18 UTC
Domain Last Updated Date:10-Apr-2012 20:50:20 UTC
Domain Expiration Date:09-Feb-2013 21:17:18 UTC
Last Transferred Date:
Sponsoring Registrar:eNom Inc R32-ME
Created by:eNom Inc R32-ME
Last Updated by Registrar:Afilias R54-ME
Domain Status:CLIENT TRANSFER PROHIBITED
Registrant ID:a1ff0a936b85ab27
Registrant Name:WhoisGuard Protected
Registrant Organization:WhoisGuard
Registrant Address:11400 W. Olympic Blvd. Suite 200
Registrant Address2:
Registrant Address3:
Registrant City:Los Angeles
Registrant State/Province:CA
Registrant Country/Economy:US
Registrant Postal Code:90064
Registrant Phone:+1.6613102107
Registrant Phone Ext.:
Registrant FAX:
Registrant FAX Ext.:
Registrant E-mail: email
Admin ID:0a97b5c0bb5499b2
Admin Name:WhoisGuard Protected
Admin Organization:WhoisGuard
Admin Address:11400 W. Olympic Blvd. Suite 200
Admin Address2:
Admin Address3:
Admin City:Los Angeles
Admin State/Province:CA
Admin Country/Economy:US
Admin Postal Code:90064
Admin Phone:+1.6613102107
Admin Phone Ext.:
Admin FAX:
Admin FAX Ext.:
Admin E-mail: email
Tech ID:f195ec9c6b85ab27
Tech Name:WhoisGuard Protected
Tech Organization:WhoisGuard
Tech Address:11400 W. Olympic Blvd. Suite 200
Tech Address2:
Tech Address3:
Tech City:Los Angeles
Tech State/Province:CA
Tech Country/Economy:US
Tech Postal Code:90064
Tech Phone:+1.6613102107
Tech Phone Ext.:
Tech FAX:
Tech FAX Ext.:
Tech E-mail: email
Nameservers:NS3.1GBITSERVER.COM
Nameservers:NS4.1GBITSERVER.COM
Nameservers:
Nameservers:
Nameservers:
Nameservers:
Nameservers:
Nameservers:
Nameservers:
Nameservers:
Nameservers:
Nameservers:
Nameservers:


DNS Analysis


DNS servers
ns3.1gbitserver.com [85.17.12.100]
ns4.1gbitserver.com [85.17.12.100]


DNS Records

Answer records
thiruttuvcd.me TXT v=spf1 +a +mx +ip4:85.17.12.100 ?all 14400s
thiruttuvcd.me MX
preference: 0
exchange: thiruttuvcd.me
14400s
thiruttuvcd.me SOA
server: ns3.1gbitserver.com
email: dnsadmin@serv.1gbitserver.com
serial: 2012111701
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
thiruttuvcd.me NS  ns3.1gbitserver.com 86400s
thiruttuvcd.me NS  ns4.1gbitserver.com 86400s
thiruttuvcd.me A 85.17.12.100 14400s

Authority records

Additional records
thiruttuvcd.me A 85.17.12.100 14400s
ns3.1gbitserver.com A 85.17.12.100 14400s
ns4.1gbitserver.com A 85.17.12.100 14400s

IP 108.162.203.245 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 108.162.203.245

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 17 Errors
  • 4 Warnings
Ratio Text/Html
  • 0.7988134587676922
Message Error
  • Error Line 55, Column 16: there is no attribute "property"
    <meta property='og:title' content='' /><meta property='og:site_name' content='W…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 55, Column 303: end tag for "meta" omitted, but OMITTAG NO was specified
    …type' content='article' /><meta property='fb:app_id' content='148065591931758'>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 55, Column 250: start tag was here
    …roperty='og:type' content='article' /><meta property='fb:app_id' content='1480…
  • Error Line 58, Column 20: document type does not allow element "div" here; assuming missing "object" start-tag
    <div align="center"><noscript>
  • Warning Line 82, Column 41: character "&" is the first character of a delimiter but occurred as data
    …		if (event.srcElement.type != "text" && event.srcElement.type != "textarea" &…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 82, Column 42: character "&" is the first character of a delimiter but occurred as data
    …	if (event.srcElement.type != "text" && event.srcElement.type != "textarea" &&…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 82, Column 80: character "&" is the first character of a delimiter but occurred as data
    …& event.srcElement.type != "textarea" && event.srcElement.type != "password") …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 82, Column 81: character "&" is the first character of a delimiter but occurred as data
    …& event.srcElement.type != "textarea" && event.srcElement.type != "password") {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 98, Column 19: character "&" is the first character of a delimiter but occurred as data
        if (e.ctrlKey && (e.which == 65 || e.which == 67 || e.which == 85 || e.whic…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 98, Column 20: character "&" is the first character of a delimiter but occurred as data
        if (e.ctrlKey && (e.which == 65 || e.which == 67 || e.which == 85 || e.whic…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 103, Column 23: character "&" is the first character of a delimiter but occurred as data
            if (e.ctrlKey && (e.which == 65 || e.which == 67 || e.which == 85 || e.…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 103, Column 24: character "&" is the first character of a delimiter but occurred as data
            if (e.ctrlKey && (e.which == 65 || e.which == 67 || e.which == 85 || e.…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 129, Column 45: document type does not allow element "meta" here
    <meta http-equiv="imagetoolbar" content="no">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 129, Column 46: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="imagetoolbar" content="no">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 129, Column 1: start tag was here
    <meta http-equiv="imagetoolbar" content="no">
  • Error Line 135, Column 23: document type does not allow element "style" here
    <style type="text/css">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 140, Column 23: document type does not allow element "style" here
    <style type="text/css">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 145, Column 7: end tag for "object" omitted, but OMITTAG NO was specified
    </head>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 58, Column 1: start tag was here
    <div align="center"><noscript>
  • Error Line 209, Column 52: there is no attribute "data-visible"
    <div class="srr-wrap  srr-style-dark" data-visible="7" data-id="srr-tab-"><div>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 209, Column 64: there is no attribute "data-id"
    <div class="srr-wrap  srr-style-dark" data-visible="7" data-id="srr-tab-"><div>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 232, Column 81: end tag for "br" omitted, but OMITTAG NO was specified
    …div><div id="text-5" class="widget_text">			<div class="textwidget"><p><br></p>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 232, Column 74: start tag was here
    …div><div id="text-5" class="widget_text">			<div class="textwidget"><p><br></p>
  • Error Line 233, Column 331: end tag for element "span" which is not open
    …2/08/thiruttumasala.com_.jpg" alt="" width="300" height="250" /></span></a></p>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 578, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center><script type="text/javascript" src="http://widget.supercounters.com/fla…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 578, Column 190: end tag for "br" omitted, but OMITTAG NO was specified
    …ascript">sc_flag(241092,"FFFFFF","000000","cccccc",2,10,0,0)</script><br><br />

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 578, Column 186: start tag was here
    …ascript">sc_flag(241092,"FFFFFF","000000","cccccc",2,10,0,0)</script><br><br />
  • Error Line 580, Column 12: end tag for "p" omitted, but OMITTAG NO was specified
    <p></center><br />

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 580, Column 1: start tag was here
    <p></center><br />

Visitor Analysis

Daily Visitor
  • 12.250 visits

In Page Analysis