Green Dot is a leading provider of reloadable prepaid cards that can be used anywhere MasterCard or Visa debit cards are accepted. Free direct deposit. No credit check. No bank account required. ...

greendot.com
  • Domain Name
    greendot.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #14881
  • Page Size
    49.9 KB
  • Ip Address
    208.87.176.35
  • Heading
    H1: 1, H2: 8, H3: 23, H4: 16, H5: 5, H6: 4
  • Images
    0 GIF, 3 JPG, 19 PNG

Website Meta Analysis

  • Title
    Prepaid Debit Card | Prepaid Visa and MasterCard | Green Dot Corporation
  • Meta Keyword
  • Meta Description
    Green Dot is a leading provider of reloadable prepaid cards that can be used anywhere MasterCard or Visa debit cards are accepted. Free direct deposit. No credit check. No bank account required.

Technical Analysis

  • Webserver
  • Ip Address
    208.87.176.35
  • Domain Age
    15 Years, 8 Months, 15 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 28 Jun 2013 07:03:26 GMT
  • rev.res: c5c775a6400edb12ea37310cea63bd6c
  • x-powered-by: ASP.NET
  • x-aspnet-version: 4.0.30319
  • x-aspnetmvc-version: 4.0
  • cache-control: no-cache
  • 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 at any time.

Registrant:
Green Dot Corporation
Admin Role
P.O. Box 1187
Monrovia, CA 91016
US
Email: email

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

Domain Name: greendot.com

Created on..............: Mon, Nov 03, 1997
Expires on..............: Mon, Nov 02, 2015
Record last updated on..: Mon, Oct 25, 2010

Administrative,Technical Contact:
Green Dot Corporation
Admin Role
P.O. Box 1187
Monrovia, CA 91016
US
Phone: +1.6267753427
Email: email

DNS Servers:

ns2.greendotdns.com
ns1.greendotdns.com


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

DNS Analysis


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


DNS Records

Answer records
greendot.com SOA
server: ns1.greendotdns.com
email: adminrole@greendotcorp.com
serial: 2009080470
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 86400
86400s
greendot.com NS  ns1.greendotdns.com 86400s
greendot.com NS  ns2.greendotdns.com 86400s
greendot.com A 208.87.176.35 600s
greendot.com MX
preference: 20
exchange: mx2.greendot.com
86400s
greendot.com MX
preference: 30
exchange: mx3.greendot.com
86400s
greendot.com MX
preference: 10
exchange: mx1.greendot.com
86400s
greendot.com TXT v=spf1 mx mx:mx1.greendot.com mx:mx2.greendot.com include:spf.cashedge.com ~all 60s

Authority records

Additional records
ns1.greendotdns.com A 208.87.176.50 86400s
ns2.greendotdns.com A 66.116.101.70 86400s
mx1.greendot.com A 67.131.213.59 86400s
mx2.greendot.com A 66.116.101.109 86400s
mx3.greendot.com A 208.87.176.100 86400s

IP 208.87.176.35 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 208.87.176.35"
    #
    # Use "?" to get help.
    #

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

    NetRange: 208.87.176.0 - 208.87.179.255
    CIDR: 208.87.176.0/22
    OriginAS: AS209, AS2828, AS23005
    NetName: GDCNET---GREEN-DOT-CORPORATION-NETWORK
    NetHandle: NET-208-87-176-0-1
    Parent: NET-208-0-0-0-0
    NetType: Direct Assignment
    Comment: http://www.greendotcorp.com
    RegDate: 2008-02-26
    Updated: 2012-02-24
    Ref: http://whois.arin.net/rest/net/NET-208-87-176-0-1

    OrgName: Green Dot Corporation
    OrgId: GDC-48
    Address: PO BOX 1187
    City: Monrovia
    StateProv: CA
    PostalCode: 91017
    Country: US
    RegDate: 2006-10-06
    Updated: 2008-02-26
    Comment: http://www.greendotcorp.com
    Ref: http://whois.arin.net/rest/org/GDC-48

    OrgTechHandle: ADMIN1283-ARIN
    OrgTechName: Admin Role
    OrgTechPhone: +1-626-775-3400
    OrgTechEmail: adminrole@greendotcorp.com
    OrgTechRef: http://whois.arin.net/rest/poc/ADMIN1283-ARIN

    OrgAbuseHandle: ADMIN1283-ARIN
    OrgAbuseName: Admin Role
    OrgAbusePhone: +1-626-775-3400
    OrgAbuseEmail: adminrole@greendotcorp.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/ADMIN1283-ARIN

    RTechHandle: ADMIN1283-ARIN
    RTechName: Admin Role
    RTechPhone: +1-626-775-3400
    RTechEmail: adminrole@greendotcorp.com
    RTechRef: http://whois.arin.net/rest/poc/ADMIN1283-ARIN

    #
    # 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
  • 39 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.53214026980988
Message Error
  • Warning Line 32, Column 487: character "&" is the first character of a delimiter but occurred as data
    …{ var a = this.readyState; if (d || a && a != "complete" && a != "loaded") ret…

    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 32, Column 488: character "&" is the first character of a delimiter but occurred as data
    … var a = this.readyState; if (d || a && a != "complete" && a != "loaded") retu…

    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 32, Column 506: character "&" is the first character of a delimiter but occurred as data
    …yState; if (d || a && a != "complete" && a != "loaded") return; d = true; clea…

    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 32, Column 507: character "&" is the first character of a delimiter but occurred as data
    …State; if (d || a && a != "complete" && a != "loaded") return; d = true; clear…

    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 63, Column 166: there is no attribute "border"
    …r Cash Reload Sweepstakes" usemap="#Image-Maps_6201302081728167" border="0"  />

    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 68, Column 95: an attribute specification must start with a name or name token
    …ef="greendot/page/breakfreefrombills#"" alt="$20,000 sweepstakes" title="$20,0…

    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 68, Column 96: end tag for "area" omitted, but OMITTAG NO was specified
    …f="greendot/page/breakfreefrombills#"" alt="$20,000 sweepstakes" title="$20,00…

    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 68, Column 13: start tag was here
                <area shape="rect" coords="500,20,630,50" href="greendot/page/break…
  • Error Line 68, Column 97: character data is not allowed here
    …="greendot/page/breakfreefrombills#"" alt="$20,000 sweepstakes" title="$20,000…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 92, Column 54: there is no attribute "data-modal"
    … <a href="/greendot/login" data-modal="#modal-signup" class="link-samepage btn…

    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 114, Column 184: there is no attribute "from"
    …rd but, don't have a User ID? <a from="landingpage" href="/greendot/create-use…

    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 117, Column 63: there is no attribute "autocomplete"
    …dot/login" method="post" autocomplete="off"><input name="__RequestVerification…

    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 117, Column 269: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …3_O7ThNhPOrg2cpX898Wt-mgIN388LcjcxS_LlCt0JB2kLdF95EFjUUk_Np0lxVxeZza3cPBdg2" />

    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 121, Column 54: there is no attribute "data-val"
    …el><input class="loginInput" data-val="true" data-val-length="" data-val-lengt…

    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 121, Column 77: there is no attribute "data-val-length"
    …nput" data-val="true" data-val-length="" data-val-length-max="12" data-val-req…

    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 121, Column 100: there is no attribute "data-val-length-max"
    …ata-val-length="" data-val-length-max="12" data-val-required="Please enter the…

    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 121, Column 123: there is no attribute "data-val-required"
    …val-length-max="12" data-val-required="Please enter the User ID you have previ…

    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 121, Column 282: there is no attribute "placeholder"
    …Model.TxtAccountNoOrUserId" placeholder="" tabindex="1" type="text" value="" />

    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 168, Column 24: there is no attribute "data-question"
        <div data-question="question1" class="question question1">How much do you p…

    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 240, Column 208: an attribute specification must start with a name or name token
    …span></p><a href="#section-form-outer"" class="link-samepage link action">Get …

    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 257, Column 341: there is no attribute "target"
    …oneypass.com/atm-locator.aspx" target="_blank" class="link action">Find ATM <s…

    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 361, Column 43: there is no attribute "data-videoid"
    …<div id="backstagevideo" data-videoid="backstagevideo" data-video="TzY7wu_agAw…

    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 361, Column 71: there is no attribute "data-video"
    …a-videoid="backstagevideo" data-video="TzY7wu_agAw" data-videowidth="640" data…

    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 361, Column 101: there is no attribute "data-videowidth"
    …a-video="TzY7wu_agAw" data-videowidth="640" data-videoheight="360" class="yt">…

    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 361, Column 124: there is no attribute "data-videoheight"
    …eo="TzY7wu_agAw" data-videowidth="640" data-videoheight="360" class="yt"></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 419, Column 20: document type does not allow element "blockquote" here; missing one of "object", "ins", "del", "map", "button" start-tag
            <blockquote>A Green Dot prepaid debit card gives you the security of ca…

    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 419, Column 21: character data is not allowed here
            <blockquote>A Green Dot prepaid debit card gives you the security of ca…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 421, Column 20: document type does not allow element "blockquote" here; missing one of "object", "ins", "del", "map", "button" start-tag
            <blockquote>Green Dot is the clear choice for a checking account altern…

    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 421, Column 21: character data is not allowed here
            <blockquote>Green Dot is the clear choice for a checking account altern…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 423, Column 20: document type does not allow element "blockquote" here; missing one of "object", "ins", "del", "map", "button" start-tag
            <blockquote>I like Green Dot … I think they are one of the good guys</b…

    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 423, Column 21: character data is not allowed here
            <blockquote>I like Green Dot … I think they are one of the good guys</b…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 437, Column 79: document type does not allow element "a" here; assuming missing "li" start-tag
    …modal-fees" class="link link-samepage">check out our simple fee plan <span cla…
  • Error Line 438, Column 9: end tag for "li" omitted, but OMITTAG NO was specified
        </ul>

    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 437, Column 31: start tag was here
          <!-- make this bigger--><a href="#modal-fees" class="link link-samepage">…
  • Error Line 439, Column 54: an attribute specification must start with a name or name token
    …"action"><a href="#section-form-outer"" class="link-samepage btn"><span>get my…

    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 526, Column 38: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
                <div class="expanded-btn">

    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 527, Column 183: there is no attribute "data-val-regex"
    …ed="Zip Code Required" data-val-regex="Valid Zip Code Required" data-val-regex…

    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 527, Column 232: there is no attribute "data-val-regex-pattern"
    …regex="Valid Zip Code Required" data-val-regex-pattern="\d{5}" class="atmzip"/>

    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 530, Column 79: there is no attribute "data-valmsg-for"
    … Stores</button><span data-valmsg-for="ZipCode" data-valmsg-replace="true" cla…

    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 530, Column 109: there is no attribute "data-valmsg-replace"
    …msg-for="ZipCode" data-valmsg-replace="true" class="field-validation-valid hea…

    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 548, Column 320: character "&" is the first character of a delimiter but occurred as data
    …d. You must have a GD online account. Carrier msg & data rates apply.”</a></li>

    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 591, Column 343: character "&" is the first character of a delimiter but occurred as data
    …gbank=lpd">Site Terms of Use, Privacy & Security</a>&nbsp;|&nbsp; <a href="/gr…

    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 643, Column 12: required attribute "type" not specified
        <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 660, Column 218: document type does not allow element "img" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "address", "fieldset", "ins", "del" start-tag
    …script&amp;WT.js=No&amp;WT.tv=10.2.29&amp;dcssip=www.greendot.com"/></noscript>

    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 665, Column 13: there is no attribute "src"
    <iframe src="https://www.cdn-gdc.com/content/track/greendot/?path=%2fgreendot&c…

    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 665, Column 79: cannot generate system identifier for general entity "culture"
    …tent/track/greendot/?path=%2fgreendot&culture=en-us" height="10" width="10" fr…

    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 665, Column 79: general entity "culture" not defined and no default entity
    …tent/track/greendot/?path=%2fgreendot&culture=en-us" height="10" width="10" fr…

    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 665, Column 86: reference not terminated by REFC delimiter
    …ack/greendot/?path=%2fgreendot&culture=en-us" height="10" width="10" framebord…

    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 665, Column 86: reference to external entity in attribute value
    …ack/greendot/?path=%2fgreendot&culture=en-us" height="10" width="10" framebord…

    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 665, Column 86: reference to entity "culture" for which no system identifier could be generated
    …ack/greendot/?path=%2fgreendot&culture=en-us" height="10" width="10" framebord…

    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 665, Column 78: entity was defined here
    …ntent/track/greendot/?path=%2fgreendot&culture=en-us" height="10" width="10" f…
  • Error Line 665, Column 101: there is no attribute "height"
    …ath=%2fgreendot&culture=en-us" height="10" width="10" frameborder="0" style="d…

    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 665, Column 112: there is no attribute "width"
    …ndot&culture=en-us" height="10" width="10" frameborder="0" style="display:none…

    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 665, Column 129: there is no attribute "frameborder"
    …e=en-us" height="10" width="10" frameborder="0" style="display:none"></iframe> 

    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 665, Column 139: there is no attribute "style"
    …e=en-us" height="10" width="10" frameborder="0" style="display:none"></iframe> 

    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 665, Column 153: element "iframe" undefined
    …e=en-us" height="10" width="10" frameborder="0" style="display:none"></iframe> 

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

Visitor Analysis

Daily Visitor
  • 8.283 visits
Daily Visitor