Watch the latest Christian videos and gospel videos with other believers of Christ at GodVine. ...

godvine.com
  • Domain Name
    godvine.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #4227
  • Page Size
    35.9 KB
  • Ip Address
    216.155.133.8
  • Heading
    H1: 1, H2: 3, H3: 16, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 18 JPG, 1 PNG

Website Meta Analysis

  • Title
    Christian Videos, Gospel Videos - GodVine
  • Meta Keyword
    christian videos, gospel videos, christian pictures, christian community, religious videos, religious pictures, christianity, god
  • Meta Description
    Watch the latest Christian videos and gospel videos with other believers of Christ at GodVine.

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    216.155.133.8
  • Domain Age
    3 Years, 0 Months, 6 days.
  • Javascript Library
    jquery, prototype
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Thu, 12 Sep 2013 23:33:13 GMT
  • server: Apache
  • x-powered-by: PHP/5.2.17
  • p3p: CP=CAO PSA OUR
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 9291
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

Corporation Service Company(c) (CSC) The Trusted Partner of More than 50% of the 100 Best Global Brands.

Contact us to learn more about our enterprise solutions for Global Domain Name Registration and Management, Trademark Research and Watching, Brand, Logo and Auction Monitoring, as well SSL Certificate Services and DNS Hosting.

NOTICE: You are not authorized to access or query our WHOIS database through the use of high-volume, automated, electronic processes or for the purpose or purposes of using the data in any manner that violates these terms of use. The Data in the CSC WHOIS database is provided by CSC for information purposes only, and to assist persons in obtaining information about or related to a domain name registration record. CSC does not guarantee its accuracy. By submitting a WHOIS query, you agree to abide by the following terms of use: you agree that you may use this Data only for lawful purposes and that under no circumstances will you use this Data to: (1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, e-mail, telephone, or facsimile; or (2) enable high volume, automated, electronic processes that apply to CSC (or its computer systems). CSC reserves the right to terminate your access to the WHOIS database in its sole discretion for any violations by you of these terms of use. CSC reserves the right to modify these terms at any time.

Registrant:
Salem Communications Corporation
Scott Hunter
4880 Santa Rosa Road
Camarillo, CA 93012
US
Email: email

Registrar Name....: CORPORATE DOMAINS, INC.
Registrar Whois...: whois.corporatedomains.com
Registrar Homepage: www.cscprotectsbrands.com

Domain Name: godvine.com

Created on..............: Mon, Aug 23, 2010
Expires on..............: Mon, Aug 23, 2021
Record last updated on..: Sun, Oct 07, 2012

Administrative,Technical Contact:
Salem Communications Corporation
Scott Hunter
4880 Santa Rosa Road
Camarillo, CA 93012
US
Phone: +1.8059870400
Email: email

DNS Servers:

NS2.CHOOPADNS.COM
NS1.CHOOPADNS.COM


Register your domain name at http://www.cscglobal.com

DNS Analysis


DNS servers
ns1.choopadns.com [68.232.191.191]
ns2.choopadns.com [68.232.191.232]

DNS Records

Answer records
godvine.com TXT google-site-verification=kus5hN85I4kgn52oT0RXhIK2uQFmmz-KcOZr-neJl4c 120s
godvine.com SOA
server: ns1.choopa.com
email: dnsadm@choopa.com
serial: 2012120605
refresh: 14400
retry: 7200
expire: 2600000
minimum ttl: 120
120s
godvine.com NS  ns2.choopa.com 120s
godvine.com NS  ns1.choopa.com 120s
godvine.com MX
preference: 2
exchange: GODVINE.COM.S6A1.PSMTP.com
120s
godvine.com MX
preference: 4
exchange: GODVINE.COM.S6A2.PSMTP.com
120s
godvine.com MX
preference: 6
exchange: GODVINE.COM.S6B1.PSMTP.com
120s
godvine.com A 216.155.133.8 120s

Authority records

Additional records
ns1.choopa.com A 208.167.225.22 300s
ns1.choopa.com 28 [16 bytes] 300s
ns2.choopa.com A 64.237.42.82 300s
ns2.choopa.com 28 [16 bytes] 300s
GODVINE.COM.S6A1.PSMTP.com A 64.18.5.10 2078s
GODVINE.COM.S6A2.PSMTP.com A 64.18.5.11 2078s
GODVINE.COM.S6B1.PSMTP.com A 64.18.5.13 2078s

IP 216.155.133.8 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Sayreville
  • Continent Code
    08872
  • Latitude
    732
  • Longitude
    501
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 216.155.133.8"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=216.155.133.8?showDetails=true&showARIN=false&ext=netref2
    #

    Edge Interactive LLC NET-216-155-133-0-28 (NET-216-155-133-0-1) 216.155.133.0 - 216.155.133.15
    Choopa, LLC CHOOPA-NETBLK04 (NET-216-155-128-0-1) 216.155.128.0 - 216.155.159.255


    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 37 Errors
  • 9 Warnings
Ratio Text/Html
  • 0.669813887679582
Message Error
  • Error Line 5, Column 16: there is no attribute "property"
    <meta property="og:title" content="Christian Videos, Gospel Videos - GodVine"/>

    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 9, Column 54: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta property="fb:app_id" content="115316321880083">

    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 9, Column 1: start tag was here
    <meta property="fb:app_id" content="115316321880083">
  • Error Line 35, Column 50: an attribute specification must start with a name or name token
    …                		document.write('<scr' + 'ipt type="text/javascript" src="' +…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 35, Column 50: element "scr" undefined
    …                		document.write('<scr' + 'ipt type="text/javascript" src="' +…

    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 35, Column 204: delimiter "'" invalid: only S separators and TAGC allowed here
    …/1' + oasRandom + '@' + oasPositionList + '?' + oasQuery + '"></scr' + 'ipt>');
  • Error Line 52, Column 8: required attribute "type" not specified
    <script>(function (d, s, id)

    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>.

  • Warning Line 57, Column 57: cannot generate system identifier for general entity "appId"
    		js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=115316321880083";

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 57, Column 57: general entity "appId" not defined and no default entity
    		js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=115316321880083";

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 57, Column 62: reference not terminated by REFC delimiter
    		js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=115316321880083";

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 57, Column 62: reference to entity "appId" for which no system identifier could be generated
    		js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=115316321880083";

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 57, Column 56: entity was defined here
    		js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=115316321880083";
  • Error Line 64, Column 437: there is no attribute "allowTransparency"
    …low:hidden; width:90px; height:21px;" allowTransparency="true"></iframe></span>

    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 90, Column 56: end tag for "input" omitted, but OMITTAG NO was specified
    	 	 		<input type="hidden" name="action" value="login">

    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 90, Column 7: start tag was here
    	 	 		<input type="hidden" name="action" value="login">
  • Error Line 117, Column 61: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …              <p style="font-size:14px; font-weight:bold;">Join the Vine :)</p>

    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 118, Column 43: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …            <p style="margin-top:8px;"><iframe src="//www.facebook.com/plugins…

    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 119, Column 58: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                    <p style="margin-top:8px;font-size:11px;">

    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 120, Column 39: there is no attribute "allowtransparency"
                <iframe allowtransparency="true" frameborder="0" scrolling="no" src…

    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.

  • Warning Line 120, Column 155: cannot generate system identifier for general entity "show_count"
    …ow_button.html?screen_name=GodVineCom&show_count=false" style="width:155px; he…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 120, Column 155: general entity "show_count" not defined and no default entity
    …ow_button.html?screen_name=GodVineCom&show_count=false" style="width:155px; he…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 120, Column 165: reference not terminated by REFC delimiter
    …html?screen_name=GodVineCom&show_count=false" style="width:155px; height:20px;…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 120, Column 165: reference to external entity in attribute value
    …html?screen_name=GodVineCom&show_count=false" style="width:155px; height:20px;…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 120, Column 165: reference to entity "show_count" for which no system identifier could be generated
    …html?screen_name=GodVineCom&show_count=false" style="width:155px; height:20px;…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 120, Column 154: entity was defined here
    …low_button.html?screen_name=GodVineCom&show_count=false" style="width:155px; h…
  • Error Line 319, Column 77: there is no attribute "placeholder"
    … type="text" class="search_box" id="q" name="q" placeholder="Search GodVine" />

    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 336, Column 142: required attribute "alt" not specified
    …2/Medi-Share-Life-is-Stressful-300x250.jpg" style="width:300px;height:250px" />

    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 348, Column 66: required attribute "action" not specified
    		<form class="NewsletterSignup newsletterform NewsletterSidebar">

    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 352, Column 23: value of attribute "type" cannot be "email"; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
    				<input type="email" class="Email" placeholder="E-mail address" />

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 374, Column 313: end tag for "img" omitted, but OMITTAG NO was specified
    …some God - a Very Creative Skit You Will Love" width="75" height="56"></a></li>

    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 374, Column 125: start tag was here
    …Creative-Skit-You-Will-Love-439.html"><img src="http://imagecdn.godvine.com/up…
  • Error Line 379, Column 332: end tag for "img" omitted, but OMITTAG NO was specified
    …s Watching - a One Girl Flash Mob at the Mall" width="75" height="56"></a></li>

    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 379, Column 141: start tag was here
    …Girl-Flash-Mob-at-the-Mall-1422.html"><img src="http://imagecdn.godvine.com/up…
  • Error Line 384, Column 302: end tag for "img" omitted, but OMITTAG NO was specified
    …Work Together to Rescue a Tiny Trapped Kitten" width="75" height="56"></a></li>

    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 384, Column 131: start tag was here
    …escue-a-Tiny-Trapped-Kitten-772.html"><img src="http://imagecdn.godvine.com/up…
  • Error Line 389, Column 320: end tag for "img" omitted, but OMITTAG NO was specified
    …y the Greatest Surprise Father-Daughter Dance" width="75" height="56"></a></li>

    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 389, Column 132: start tag was here
    …rise-Father-Daughter-Dance-2686.html"><img src="http://imagecdn.godvine.com/up…
  • Error Line 394, Column 299: end tag for "img" omitted, but OMITTAG NO was specified
    … Choice is Yours - A Video For Anyone in Need" width="75" height="56"></a></li>

    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 394, Column 126: start tag was here
    …A-Video-For-Anyone-in-Need-1252.html"><img src="http://imagecdn.godvine.com/up…
  • Error Line 399, Column 316: end tag for "img" omitted, but OMITTAG NO was specified
    …se You - a Very Unique and Moving Performance" width="75" height="56"></a></li>

    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 399, Column 134: start tag was here
    …ique-and-Moving-Performance-981.html"><img src="http://imagecdn.godvine.com/up…
  • Error Line 405, Column 8: end tag for "span" omitted, but OMITTAG NO was specified
    		</div>

    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 404, Column 5: start tag was here
    				<span class="liltext"><a href="http://www.godvine.com/items/random/">See Mo…
  • Error Line 540, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 61, Column 3: start tag was here
      <div id="wrap">
  • Error Line 540, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 60, Column 1: start tag was here
    <div id="layout">

Visitor Analysis

Daily Visitor
  • 39.667 visits