Get your calling cards and phone cards online. Save up to 75% on long distance calling and international calling. Our international phone cards have the cheapest rates. ...

callingcardplus.com
  • Domain Name
    callingcardplus.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #426405
  • Page Size
    48.7 KB
  • Ip Address
    204.12.1.20
  • Heading
    H1: 2, H2: 7, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 7 JPG, 4 PNG

Website Meta Analysis

  • Title
    Phone Cards, Calling Cards, Prepaid Phone Card, Prepaid Calling Card from CallingCardPlus
  • Meta Keyword
    phone cards,calling cards,international calling cards,international phone cards,prepaid calling cards,prepaid phone cards
  • Meta Description
    Get your calling cards and phone cards online. Save up to 75% on long distance calling and international calling. Our international phone cards have the cheapest rates.

Technical Analysis

  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    204.12.1.20
  • Domain Age
    10 Years, 10 Months, 16 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Mon, 04 Mar 2013 02:54:07 GMT
  • server: Microsoft-IIS/6.0
  • x-powered-by: ASP.NET
  • content-length: 46786
  • content-type: text/html
  • cache-control: private
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
The results below are provided by Namescout.com.
(whois.Namescout.com)
By using Namescout.com's WHOIS database, you confirm that you understand
the following, and you agree to be bound by the terms of usage and
limitations of warranty contained herein.
Although the data contained in Namescout.com's WHOIS database is believed
by the company to be reliable, it is provided "as is". Namescout.com
provides no guarantee or warranty regarding its accuracy and will not
be held liable for any damages resulting from any inaccurate
information that may be included in the database. Namescout.com's sole
purpose for providing this information is to assist you in acquiring
information about domain name registration records. Any use of this
data for any other purpose is expressly prohibited without the prior
written permission of Namescout.com. By submitting a query to Namescout.com,
you agree to the terms contained herein and in particular, you agree
not to use this data to allow, enable, or otherwise make possible,
distribution or collection of this data, in part or in its entirety,
for any purpose, such as the transmission of unsolicited advertising
and solicitations of any kind, including spam. You further agree not to
use this data to enable high volume, automated or robotic electronic
processes designed to collect or compile this data for any purpose,
including mining this data for your own personal or commercial
purposes.
Domain Domain Name: callingcardplus.com
Created: 04/15/08
Date Updated: 10/20/10
Expires: 04/14/15
DNS1: NS1.LNHI.NET
DNS2: NS2.LNHI.NET

Registrant

TelePlus LLC
Tele Plus
5520 cherokee Ave, Suite 210
Alexandria, VA (US)
22312

Administrative Contact

TelePlus, LLC
Amr Ibrahim
5520 cherokee Ave, Suite 210
Alexandria, VA (US)
22312
email
7032259435
3054363689

Technical Contact

TelePlus, LLC
Amr Ibrahim
5520 cherokee Ave, Suite 210
Alexandria, VA (US)
22312
email
7032259435
3054363689

Registrar: Namescout.com

Register your domain now at www.Namescout.com

0

IP 204.12.1.20 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Alexandria
  • Continent Code
    22312
  • Latitude
    703
  • Longitude
    511
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 204.12.1.20"
    #
    # Use "?" to get help.
    #

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

    HostMySite HOSTMYSITE (NET-204-12-0-0-1) 204.12.0.0 - 204.12.127.255
    TelePlus LLC TELEPLUSLLC (NET-204-12-1-16-1) 204.12.1.16 - 204.12.1.31


    #
    # 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
  • 26 Errors
  • 10 Warnings
Ratio Text/Html
  • 0.690897052627355
Message Error
  • Error Line 7, Column 6: document type does not allow element "HTML" here
    <html><head>

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

  • Warning Line 10, Column 155: NET-enabling start-tag requires SHORTTAG YES
    …g cards,international phone cards,prepaid calling cards,prepaid phone cards" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 11, Column 205: NET-enabling start-tag requires SHORTTAG YES
    …ternational calling. Our international phone cards have the cheapest rates." />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 12, Column 44: NET-enabling start-tag requires SHORTTAG YES
    <meta name="robots" content="index,follow" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 13, Column 47: NET-enabling start-tag requires SHORTTAG YES
    <meta name="googlebot" content="index,follow" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 14, Column 79: NET-enabling start-tag requires SHORTTAG YES
    <meta name="verify-v1" content="1JJhc2bkIJ2W+zh6ouVtp7nArGXfR1XztRzpqscLhBM=" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 15, Column 79: NET-enabling start-tag requires SHORTTAG YES
    <meta name="verify-v1" content="gYHAd0mbwMy7kLx0fyjsPNFUk70bGo5p3QJIbuBakLk=" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 16, Column 71: NET-enabling start-tag requires SHORTTAG YES
    <meta name="msvalidate.01" content="94A8057645BAB34B15E48E5474966B3E" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 20, Column 69: NET-enabling start-tag requires SHORTTAG YES
    <link rel="stylesheet" type="text/css" href="css/contentslider.css" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 22, Column 51: required attribute "TYPE" not specified
    <script src="java/common.js" LANGUAGE="JavaScript"></script>

    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 27, Column 7: end tag for "HEAD" which is not finished
    </head>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 104, Column 49: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <div class="rm_searchButton" style="color:#FFF;"></div></a></div>

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

  • Warning Line 150, Column 93: cannot generate system identifier for general entity "FromCountry"
    …llingcardplus.com/SearchResult.asp?Country=231&FromCountry=470">India</a></div>

    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 150, Column 93: general entity "FromCountry" not defined and no default entity
    …llingcardplus.com/SearchResult.asp?Country=231&FromCountry=470">India</a></div>

    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.

  • Error Line 150, Column 104: reference to entity "FromCountry" for which no system identifier could be generated
    …llingcardplus.com/SearchResult.asp?Country=231&FromCountry=470">India</a></div>

    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 150, Column 92: entity was defined here
    …llingcardplus.com/SearchResult.asp?Country=231&FromCountry=470">India</a></div>
  • Error Line 174, Column 104: reference to entity "FromCountry" for which no system identifier could be generated
    …ngcardplus.com/SearchResult.asp?Country=170&FromCountry=470">Ethiopia</a></div>

    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 150, Column 92: entity was defined here
    …llingcardplus.com/SearchResult.asp?Country=231&FromCountry=470">India</a></div>
  • Error Line 180, Column 104: reference to entity "FromCountry" for which no system identifier could be generated
    …plus.com/SearchResult.asp?Country=357&FromCountry=470">Nigeria - Cell</a></div>

    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 150, Column 92: entity was defined here
    …llingcardplus.com/SearchResult.asp?Country=231&FromCountry=470">India</a></div>
  • Error Line 183, Column 104: reference to entity "FromCountry" for which no system identifier could be generated
    …lus.com/SearchResult.asp?Country=171&FromCountry=470">Ethiopia - Cell</a></div>

    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 150, Column 92: entity was defined here
    …llingcardplus.com/SearchResult.asp?Country=231&FromCountry=470">India</a></div>
  • Error Line 192, Column 104: reference to entity "FromCountry" for which no system identifier could be generated
    …lingcardplus.com/SearchResult.asp?Country=177&FromCountry=470">France</a></div>

    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 150, Column 92: entity was defined here
    …llingcardplus.com/SearchResult.asp?Country=231&FromCountry=470">India</a></div>
  • Error Line 240, Column 209: required attribute "ALT" not specified
    …Treasure.jpg" width="214" height="116"></a><a href="http://www.callingcardplus…

    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 243, Column 189: required attribute "ALT" not specified
    …"images/imagesNew/cards/Brillant.jpg" width="214" height="116"></a></div></div>

    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 246, Column 214: required attribute "ALT" not specified
    …magesNew/cards/Teleplus_Platinum.jpg" width="214" height="116"></a></div></div>

    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 250, Column 210: required attribute "ALT" not specified
    …/imagesNew/cards/cleanClearLarge.jpg" width="214" height="116"></a></div></div>

    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 255, Column 222: required attribute "ALT" not specified
    …Platinum.jpg" width="214" height="116"></a></div></div><div class="rm_topCards…

    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 257, Column 198: required attribute "ALT" not specified
    …ages/imagesNew/cards/AfricaHello.jpg" width="214" height="116"></a></div></div>

    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 269, Column 50: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <a href="WirelessCards.asp"><div class="rm_logos">

    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 282, Column 52: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <a href="LogIn.asp"><div class="rm_loginBt rm_left"></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 283, Column 78: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …LogIn.asp"><div class="rm_recharge rm_left" style="margin-left:5px;"></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 285, Column 150: required attribute "ALT" not specified
    …><img src="images/imagesNew/get20Extra.gif" width="257" height="177"></a></div>

    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 286, Column 143: required attribute "ALT" not specified
    …igns/"><img src="images/imagesNew/adv1.jpg" width="260" height="270"></a></div>

    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 312, Column 225: required attribute "ALT" not specified
    …com"><img src="images/imagesNew/geoTrust.png" width="98" height="47"></a></div>

    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 313, Column 53: value of attribute "ID" invalid: "3" cannot start a name
    …rgin-left:10px; margin-top:10px;" id="30801de0-66b2-4027-82d4-51208f5ed8cc"> <…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Warning Line 313, Column 582: NET-enabling start-tag requires SHORTTAG YES
    …7-4699-bbcb-52e447092e9c" alt="TRUSTe online privacy certification"/></a></div>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 314, Column 214: required attribute "ALT" not specified
    …rdplus.com/images/imagesNew/fanfacebook.png" width="160" height="43"></a></div>

    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 315, Column 207: required attribute "ALT" not specified
    …ardplus.com/images/imagesNew/fanTwitter.png" width="156" height="43"></a></div>

    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 328, Column 87: required attribute "ALT" not specified
    …xt-align:center; margin-top:5px;"><img src="images/imagesNew/ecards.png"></div>

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

Visitor Analysis

Daily Visitor
  • 350 visits
Daily Visitor