First Tech Federal Credit Union,At First Tech Federal Credit Union, we're here to introduce you to a completely different banking experience. ...

firsttechfed.com
  • Domain Name
    firsttechfed.com
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #30437
  • Page Size
    52.4 KB
  • Ip Address
    65.174.253.170
  • Heading
    H1: 0, H2: 1, H3: 8, H4: 2, H5: 7, H6: 0
  • Images
    5 GIF, 6 JPG, 2 PNG

Website Meta Analysis

  • Title
    First Tech Federal Credit Union - Home
  • Meta Keyword
    First Tech Federal Credit Union,At First Tech Federal Credit Union, we're here to introduce you to a completely different banking experience.
  • Meta Description
    First Tech Federal Credit Union,At First Tech Federal Credit Union, we're here to introduce you to a completely different banking experience.

Technical Analysis

  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    65.174.253.170
  • Domain Age
    2 Years, 9 Months, 1 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: private
  • content-length: 59366
  • content-type: text/html; charset=utf-8
  • server: Microsoft-IIS/6.0
  • x-powered-by: ASP.NET
  • x-aspnet-version: 2.0.50727
  • date: Sun, 18 Aug 2013 16:44:47 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for firsttechfed.com

DNS Analysis


DNS servers
ns11.worldnic.com [205.178.190.6]
ns12.worldnic.com [206.188.198.6]


DNS Records

Answer records
firsttechfed.com SOA
server: NS11.WORLDNIC.COM
email: namehost@WORLDNIC.COM
serial: 113012515
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
7200s
firsttechfed.com MX
preference: 60
exchange: smtp.firsttechfed.com
7200s
firsttechfed.com A 65.174.253.169 3600s
firsttechfed.com MX
preference: 20
exchange: service62-us.mimecast.com
7200s
firsttechfed.com MX
preference: 10
exchange: service61-us.mimecast.com
7200s
firsttechfed.com NS  ns12.worldnic.com 7200s
firsttechfed.com TXT v=spf1 a:service61-us.mimecast.com a:service62-us.mimecast.com include:spf.mailengine1.com ip4:72.32.227.107 ip4:63.117.120.96/27 mx ~all 7200s
firsttechfed.com NS  ns11.worldnic.com 7200s

Authority records

Additional records
smtp.firsttechfed.com A 65.174.253.172 7200s

IP 65.174.253.170 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 51 Errors
  • 29 Warnings
Ratio Text/Html
  • 0.43138605933071383
Message Error
  • Error Line 52, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

  • Error Line 202, Column 93: document type does not allow element "ul" here
    …ul class='cList' id='pro_all_accounts'><li id='pro_all'>All<input type='radio'…

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

  • Error Line 203, Column 61: document type does not allow element "div" here
    …t-page").append("<div id='dvAllAccnts'><ul class='cList'><li id='pro_all'>All&…

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

  • Error Line 203, Column 88: ID "pro_all" already defined
    …vAllAccnts'><ul class='cList'><li id='pro_all'>All&nbsp;&nbsp;<input type='rad…

    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 202, Column 102: ID "pro_all" first defined here
    …'cList' id='pro_all_accounts'><li id='pro_all'>All<input type='radio'/></li><l…
  • Error Line 203, Column 145: value of attribute "checked" cannot be "true"; must be one of "checked"
    …nbsp;<input type='radio' checked='true' name='accGrp'/></li><li id='pro_person…

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

  • Error Line 203, Column 175: ID "pro_personal" already defined
    …ed='true' name='accGrp'/></li><li id='pro_personal'>Personal&nbsp;&nbsp;<input…

    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 202, Column 148: ID "pro_personal" first defined here
    …>All<input type='radio'/></li><li id='pro_personal'>Personal<input type='radio…
  • Error Line 203, Column 257: ID "pro_business" already defined
    …e='radio' name='accGrp'/></li><li id='pro_business'>Business&nbsp;&nbsp;<input…

    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 202, Column 204: ID "pro_business" first defined here
    …onal<input type='radio'/></li><li id='pro_business'>Business<input type='radio…
  • Error Line 207, Column 46: document type does not allow element "br" here
    … $(".footerlinksp:first").append("<br/><a class='twitter' target='_blank' href…

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

  • Error Line 207, Column 120: document type does not allow element "a" here
    …href='http://twitter.com/Firsttechfed'>&nbsp;</a><br/><a class='facebook' targ…

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

  • Error Line 207, Column 135: document type does not allow element "br" here
    …itter.com/Firsttechfed'>&nbsp;</a><br/><a class='facebook' target='_blank' hre…

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

  • Error Line 207, Column 210: document type does not allow element "a" here
    …ok' target='_blank' href='http://twitter.com/Firsttechfed'>&nbsp;</a>").html();

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

  • Error Line 278, Column 44: document type does not allow element "span" here; assuming missing "li" start-tag
                        <span class="clearLeft"></span>
  • Error Line 279, Column 21: 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 278, Column 21: start tag was here
                        <span class="clearLeft"></span>
  • Error Line 378, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

  • Error Line 413, Column 125: required attribute "alt" not specified
    …firsttechfed.com/static/img/ajax-loader1.gif" style="vertical-align: middle" />

    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 482, Column 131: end tag for "img" omitted, but OMITTAG NO was specified
    …         src="https://www.firsttechfed.com/static/img/comp.jpg" class="lfloat">

    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 481, Column 57: start tag was here
    <img width="87" style="margin-right: 1em…
  • Warning Line 529, Column 53: character "<" is the first character of a delimiter but occurred as data
                if (navigator.userAgent.indexOf("iPad") <= 0) {

    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 542, Column 37: character "&" is the first character of a delimiter but occurred as data
            var regex = new RegExp("[\\?&]" + key + "=([^&#]*)");

    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 542, Column 54: character "&" is the first character of a delimiter but occurred as data
            var regex = new RegExp("[\\?&]" + key + "=([^&#]*)");

    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 562, Column 184: document type does not allow element "iframe" here
    … a + '?" width="1" height="1" frameborder="0" style="display:none"></iframe>');

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

  • Error Line 567, Column 7: required attribute "type" not specified
    <style>

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

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

  • Error Line 567, Column 7: document type does not allow element "style" here
    <style>

    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 706, Column 34: character "&" is the first character of a delimiter but occurred as data
                if (username != null && username != "") {

    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 706, Column 35: character "&" is the first character of a delimiter but occurred as data
                if (username != null && username != "") {

    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 728, Column 40: character "&" is the first character of a delimiter but occurred as data
                if ((screen.width >= 1024) && (screen.height >= 768)) {

    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 728, Column 41: character "&" is the first character of a delimiter but occurred as data
                if ((screen.width >= 1024) && (screen.height >= 768)) {

    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 746, Column 129: required attribute "alt" not specified
    …firsttechfed.com/static/img/ajax-loader1.gif" style="vertical-align: middle" />

    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 825, Column 15: required attribute "type" not specified
    						  <style>

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

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

  • Error Line 825, Column 15: document type does not allow element "style" here
    						  <style>

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

  • Error Line 868, Column 30: required attribute "type" not specified
    <script language="javascript">

    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 870, Column 44: character "@" not allowed in attribute specification list
        Copyright 2011 : Simone Gianni <simoneg@apache.org>
  • Error Line 870, Column 44: element "simoneg" undefined
        Copyright 2011 : Simone Gianni <simoneg@apache.org>

    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).
  • Warning Line 895, Column 61: character "&" is the first character of a delimiter but occurred as data
                        src += k + '=' + options.playopts[k] + '&';

    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 924, Column 39: required attribute "src" not specified
                img = $('<img align="left">');

    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 924, Column 39: required attribute "alt" not specified
                img = $('<img align="left">');

    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 924, Column 40: end tag for "img" omitted, but OMITTAG NO was specified
                img = $('<img align="left">');

    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 924, Column 22: start tag was here
                img = $('<img align="left">');
  • Warning Line 972, Column 114: cannot generate system identifier for general entity "format"
    …s.user + '/uploads?alt=json-in-script&format=5&callback=?', null, function(dat…

    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 972, Column 114: general entity "format" not defined and no default entity
    …s.user + '/uploads?alt=json-in-script&format=5&callback=?', null, function(dat…

    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 972, Column 120: reference not terminated by REFC delimiter
    …ser + '/uploads?alt=json-in-script&format=5&callback=?', null, function(data) {

    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 972, Column 120: reference to entity "format" for which no system identifier could be generated
    …ser + '/uploads?alt=json-in-script&format=5&callback=?', null, function(data) {

    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 972, Column 113: entity was defined here
    …ts.user + '/uploads?alt=json-in-script&format=5&callback=?', null, function(da…
  • Warning Line 972, Column 123: cannot generate system identifier for general entity "callback"
    …ser + '/uploads?alt=json-in-script&format=5&callback=?', null, function(data) {

    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 972, Column 123: general entity "callback" not defined and no default entity
    …ser + '/uploads?alt=json-in-script&format=5&callback=?', null, function(data) {

    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 972, Column 131: reference not terminated by REFC delimiter
    …ser + '/uploads?alt=json-in-script&format=5&callback=?', null, function(data) {

    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 972, Column 131: reference to entity "callback" for which no system identifier could be generated
    …ser + '/uploads?alt=json-in-script&format=5&callback=?', null, function(data) {

    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 972, Column 122: entity was defined here
    …ser + '/uploads?alt=json-in-script&format=5&callback=?', null, function(data) {
  • Error Line 999, Column 7: marked section end not in marked section declaration
        //]]>
  • Error Line 1002, Column 9: end tag for "div" omitted, but OMITTAG NO was specified
    </script>

    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 906, Column 26: start tag was here
                    car = $('<div>');
  • Error Line 1002, Column 9: end tag for "iframe" omitted, but OMITTAG NO was specified
    </script>

    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 888, Column 26: start tag was here
                    ifr = $('<iframe scrolling="no">');
  • Error Line 1002, Column 9: end tag for "simoneg" omitted, but OMITTAG NO was specified
    </script>

    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 870, Column 36: start tag was here
        Copyright 2011 : Simone Gianni <simoneg@apache.org>
  • Error Line 1074, Column 31: end tag for "tr" which is not finished
    							<tr class="spacer"></tr>

    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 1081, Column 31: end tag for "tr" which is not finished
    							<tr class="spacer"></tr>

    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 1088, Column 31: end tag for "tr" which is not finished
    							<tr class="spacer"></tr>

    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 1095, Column 31: end tag for "tr" which is not finished
    							<tr class="spacer"></tr>

    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.

  • Warning Line 1227, Column 77: cannot generate system identifier for general entity "dn"
    …n.com/splash?form_file=fdf/splash.fdf&dn=firsttechfed.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 1227, Column 77: general entity "dn" not defined and no default entity
    …n.com/splash?form_file=fdf/splash.fdf&dn=firsttechfed.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 1227, Column 79: reference not terminated by REFC delimiter
    …com/splash?form_file=fdf/splash.fdf&dn=firsttechfed.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 1227, Column 79: reference to external entity in attribute value
    …com/splash?form_file=fdf/splash.fdf&dn=firsttechfed.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 1227, Column 79: reference to entity "dn" for which no system identifier could be generated
    …com/splash?form_file=fdf/splash.fdf&dn=firsttechfed.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 1227, Column 76: entity was defined here
    …gn.com/splash?form_file=fdf/splash.fdf&dn=firsttechfed.com&lang=en" target="_b…
  • Warning Line 1227, Column 101: reference not terminated by REFC delimiter
    …df/splash.fdf&dn=firsttechfed.com&lang=en" target="_blank"><img src="https://w…

    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 1249, Column 103: there is no attribute "border"
    …me="ctl00$Footer1$txtfrom" type="text" id="ctl00_Footer1_txtfrom" border="1" />

    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 452, Column 61: reference to non-existent ID "password"
    …                                         <label for="password">PASSWORD</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 763, Column 53: reference to non-existent ID "password"
                                            <label for="password">PASSWORD</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 445, Column 61: reference to non-existent ID "username"
    …                                         <label for="username">USERNAME</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 760, Column 25: reference to non-existent ID "username"
    							     <label for="username">USERNAME</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

Visitor Analysis

Daily Visitor
  • 6.300 visits