home Home Browse Movies Latest Movies Featured Movies Popular Movies Login Login Signup for a Free Trial Now! Username Password Veirfy Password Accept Terms and Conditions and Refund Policy Questions? 1-800-851-7935 info@123vidz.com Featured ...

123vidz.com
  • Domain Name
    123vidz.com
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #7185
  • Page Size
    8.4 KB
  • Ip Address
    209.200.152.30
  • Heading
    H1: 1, H2: 2, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 1 JPG, 6 PNG

Website Meta Analysis

  • Title
    123vidz - Watch Movies Instantly Online
  • Meta Keyword
  • Meta Description
    home Home Browse Movies Latest Movies Featured Movies Popular Movies Login Login Signup for a Free Trial Now! Username Password Veirfy Password Accept Terms and Conditions and Refund Policy Questions? 1-800-851-7935 info@123vidz.com Featured ...

Technical Analysis

  • Webserver
    nginx/1.1.19
  • Ip Address
    209.200.152.30
  • Domain Age
    1 Years, 8 Months, 18 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from 123vidz.com.

HTML Analysis

  • server: nginx/1.1.19
  • date: Wed, 28 Aug 2013 21:06:35 GMT
  • content-type: text/html; charset=UTF-8
  • nncoection: close
  • expires: Mon, 26 Jul 1997 05:00:00 GMT
  • last-modified: Wed, 28 Aug 2013 21:06:35 GMT
  • cache-control: no-store, no-cache, must-revalidate
  • pragma: no-cache
  • p3p: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
9227-6476 Quebec Inc.

Domain Name: 123VIDZ.COM

Domain servers in listed order:
NS65.DOMAINCONTROL.COM
NS66.DOMAINCONTROL.COM

DNS Analysis


DNS servers
ns1.enduringhost.com [199.180.248.49]
ns2.enduringhost.com [184.82.238.36]
nsuk.enduringhost.com [46.37.185.240]
nsin.enduringhost.com [175.101.0.136]


DNS Records

Answer records
123vidz.com TXT v=spf1 a mx ~all 7200s
123vidz.com MX
preference: 1
exchange: aspmx.l.google.com
7200s
123vidz.com MX
preference: 5
exchange: alt1.aspmx.l.google.com
7200s
123vidz.com MX
preference: 5
exchange: alt2.aspmx.l.google.com
7200s
123vidz.com MX
preference: 10
exchange: aspmx2.googlemail.com
7200s
123vidz.com MX
preference: 10
exchange: aspmx3.googlemail.com
7200s
123vidz.com SOA
server: ns1.enduringhost.com
email: vincare@gmail.com
serial: 2012101600
refresh: 1200
retry: 7200
expire: 1209600
minimum ttl: 3600
3600s
123vidz.com NS  nsin.enduringhost.com 3600s
123vidz.com NS  nsuk.enduringhost.com 3600s
123vidz.com NS  ns1.enduringhost.com 3600s
123vidz.com NS  ns2.enduringhost.com 3600s
123vidz.com A 209.200.152.30 7200s

Authority records

Additional records
ns1.enduringhost.com A 199.180.248.49 14400s
ns2.enduringhost.com A 184.82.238.36 14400s
nsin.enduringhost.com A 175.101.0.136 14400s
nsuk.enduringhost.com A 46.37.185.240 14400s

IP 209.200.152.30 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 19 Errors
  • 0 Warnings
Ratio Text/Html
  • 0.7353351955307262
Message Error
  • Error Line 7, Column 46: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="Pragma" content="no-cache">

    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 7, Column 1: start tag was here
    <meta http-equiv="Pragma" content="no-cache">
  • Error Line 8, Column 41: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="Expires" content="-1">

    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 8, Column 1: start tag was here
    <meta http-equiv="Expires" content="-1">
  • Error Line 36, Column 7: required attribute "type" not specified
    <style>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 47, Column 6: element "HEAD" undefined
    <HEAD>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 48, Column 18: there is no attribute "HTTP-EQUIV"
    <META HTTP-EQUIV="Pragma" CONTENT="no-cache">

    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 48, Column 35: there is no attribute "CONTENT"
    <META HTTP-EQUIV="Pragma" CONTENT="no-cache">

    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 48, Column 45: element "META" undefined
    <META HTTP-EQUIV="Pragma" CONTENT="no-cache">

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 49, Column 40: element "META" undefined
    <META HTTP-EQUIV="Expires" CONTENT="-1">

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 50, Column 7: end tag for "META" 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 49, Column 1: start tag was here
    <META HTTP-EQUIV="Expires" CONTENT="-1">
  • Error Line 50, Column 7: end tag for "META" 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 48, Column 1: start tag was here
    <META HTTP-EQUIV="Pragma" CONTENT="no-cache">
  • Error Line 76, Column 22: syntax of attribute value does not conform to declared value
    <a title="Login" id="" class="mega login" href="/users/loginpage"><div style='m…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 76, Column 105: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … href="/users/loginpage"><div style='margin-top:6px;color:#777'>Login</div></a>

    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 126, Column 150: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ecastcdn.net/8051D5/img//img/genre/horror/111.png" alt="" width=152 /></a></li>
  • Error Line 127, Column 150: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ecastcdn.net/8051D5/img//img/genre/horror/222.png" alt="" width=152 /></a></li>
  • Error Line 128, Column 150: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ecastcdn.net/8051D5/img//img/genre/horror/333.png" alt="" width=152 /></a></li>
  • Error Line 129, Column 150: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ecastcdn.net/8051D5/img//img/genre/horror/444.png" alt="" width=152 /></a></li>
  • Error Line 130, Column 150: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ecastcdn.net/8051D5/img//img/genre/horror/555.png" alt="" width=152 /></a></li>
  • Error Line 131, Column 150: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ecastcdn.net/8051D5/img//img/genre/horror/777.png" alt="" width=152 /></a></li>
  • Error Line 153, Column 62: end tag for element "a" which is not open
              <li><a href="/affiliates/contact">Affiliates</a></a></li>

    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.

Visitor Analysis

Daily Visitor
  • 29.167 visits