Please enter a 5 digit zip code Home About MoneyPak Reload a Prepaid Card Add Money to PayPal Make a Payment Add Funds to Serve Cash Deposit Use a MoneyPak Reload a Prepaid ...

moneypak.com
  • Domain Name
    moneypak.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #27433
  • Page Size
    22.7 KB
  • Ip Address
    66.116.101.101
  • Heading
    H1: 5, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    7 GIF, 1 JPG, 1 PNG

Website Meta Analysis

  • Title
    Green Dot - MoneyPak
  • Meta Keyword
  • Meta Description
    Please enter a 5 digit zip code Home About MoneyPak Reload a Prepaid Card Add Money to PayPal Make a Payment Add Funds to Serve Cash Deposit Use a MoneyPak Reload a Prepaid Card Add Money to PayPal Make a Payment Add Funds to Serve Cash Deposit ...

Technical Analysis

  • Webserver
  • Ip Address
    66.116.101.101
  • Domain Age
    7 Years, 0 Months, 8 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sat, 02 Feb 2013 23:38:14 GMT
  • x-powered-by: ASP.NET
  • x-aspnet-version: 2.0.50727
  • x-aspnetmvc-version: 1.0
  • cache-control: no-cache, no-store, must-revalidate
  • pragma: no-cache
  • expires: -1
  • content-type: text/html; charset=utf-8
  • vary: Accept-Encoding
  • content-encoding: gzip
  • 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

DNS Analysis


DNS servers
ns1.greendotdns.com [208.87.176.50]
ns2.greendotdns.com [66.116.101.70]


DNS Records

Answer records
moneypak.com SOA
server: ns1.greendotdns.com
email: adminrole@greendotcorp.com
serial: 2009031734
refresh: 10800
retry: 3600
expire: 2592000
minimum ttl: 86400
0s
moneypak.com NS  ns1.greendotdns.com 86400s
moneypak.com NS  ns2.greendotdns.com 86400s
moneypak.com A 66.116.101.101 600s

Authority records

Additional records
ns2.greendotdns.com A 66.116.101.70 86400s
ns1.greendotdns.com A 208.87.176.50 86400s

IP 66.116.101.101 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Monrovia
  • Continent Code
    91017
  • Latitude
    626
  • Longitude
    803
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 66.116.101.101"
    #
    # Use "?" to get help.
    #

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

    SWITCH Communications Group LLC SWITCH-COMMUNICATIONS (NET-66-116-96-0-1) 66.116.96.0 - 66.116.127.255
    Green Dot Corporation GREENDOTCORPORATION-101 (NET-66-116-101-64-1) 66.116.101.64 - 66.116.101.127


    #
    # 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
  • 6 Errors
  • 5 Warnings
Ratio Text/Html
  • 0.5212802619109158
Message Error
  • Error Line 347, Column 30: there is no attribute "autocomplete"
             <input autocomplete="off" id="AccountNum" maxlength="19" name="Account…

    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 348, Column 17: there is no attribute "tip"
             <a tip="{'div':'#tip_homeCalloutLeft','top':29,'left':28}" href="javas…

    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 509, Column 47: ID "A6" already defined
                <a href="/AboutGreenDot.aspx" id="A6">About Us</a> |

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 506, Column 50: ID "A6" first defined here
                <a href="/ProtectYourMoney.aspx" id="A6">Protect Your Money</a> 
  • Warning Line 517, Column 80: cannot generate system identifier for general entity "dn"
    …splash?form_file=fdf/thawtesplash.fdf&dn=WWW.MONEYPAK.COM&lang=en" target="_bl…

    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 517, Column 80: general entity "dn" not defined and no default entity
    …splash?form_file=fdf/thawtesplash.fdf&dn=WWW.MONEYPAK.COM&lang=en" target="_bl…

    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 517, Column 82: reference not terminated by REFC delimiter
    …lash?form_file=fdf/thawtesplash.fdf&dn=WWW.MONEYPAK.COM&lang=en" target="_blan…

    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 517, Column 82: reference to external entity in attribute value
    …lash?form_file=fdf/thawtesplash.fdf&dn=WWW.MONEYPAK.COM&lang=en" target="_blan…

    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 517, Column 82: reference to entity "dn" for which no system identifier could be generated
    …lash?form_file=fdf/thawtesplash.fdf&dn=WWW.MONEYPAK.COM&lang=en" target="_blan…

    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 517, Column 79: entity was defined here
    …esplash?form_file=fdf/thawtesplash.fdf&dn=WWW.MONEYPAK.COM&lang=en" target="_b…
  • Warning Line 517, Column 104: reference not terminated by REFC delimiter
    …sh?form_file=fdf/thawtesplash.fdf&dn=WWW.MONEYPAK.COM&lang=en" target="_blank">

    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 561, Column 14: end tag for element "asp:Content" which is not open
    </asp:Content>

    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
  • 6.650 visits
Daily Visitor