HOME ENROLLMENT MY PROFILE PAYMENTS HELP & INFORMATION CONTACT US LOGIN ABOUT EFTPS HOW TO USE EFTPS FAQ WHAT'S NEW? PRIVACY STATEMENT ACCESSIBILITY STATEMENT Please note: Your tax payment is due regardless of ...

eftps.gov
  • Domain Name
    eftps.gov
  • Favicon
  • Google Page Rank
    7
  • Alexa Rank
    #12197
  • Page Size
    11.1 KB
  • Ip Address
    204.194.124.20
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 5 PNG

Website Meta Analysis

  • Title
    Welcome to EFTPS online
  • Meta Keyword
  • Meta Description
    HOME ENROLLMENT MY PROFILE PAYMENTS HELP & INFORMATION CONTACT US LOGIN ABOUT EFTPS HOW TO USE EFTPS FAQ WHAT'S NEW? PRIVACY STATEMENT ACCESSIBILITY STATEMENT Please note: Your tax payment is due regardless of this Web site's availability. ...

Technical Analysis

  • Webserver
    IBM_HTTP_Server
  • Ip Address
    204.194.124.20
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from eftps.gov.

HTML Analysis

  • date: Thu, 05 Sep 2013 18:07:03 GMT
  • server: IBM_HTTP_Server
  • optr_cxt: 010005000013ea8d0f-5921-4f3d-85e4-04addcfc99d5c26a0790-2c52-43ff-955b-e634e2d5008650c409ab-2b68-45a1-8370-5b30cdc26c06HTTP ;
  • expires: Thu, 01 Dec 1994 16:00:00 GMT
  • cache-control: no-cache="set-cookie, set-cookie2"
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-type: text/html
  • content-language: en-US
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% DOTGOV WHOIS Server ready
Domain Name: EFTPS.GOV
Status: ACTIVE


>>> Last update of whois database: Wed, 26 Sep 2012 23:05:16 UTC

DNS Analysis


DNS servers
ns5.eftps.com [204.194.122.205]
ns6.eftps.com
ns10.eftps.com [12.36.213.171]
ns11.eftps.com [12.36.213.172]


DNS Records

Answer records
eftps.gov A 204.194.124.20 600s
eftps.gov 28 [16 bytes] 600s
eftps.gov SOA
server: unknown
email: domainadmin@eftps.com
serial: 787
refresh: 10800
retry: 1080
expire: 2592000
minimum ttl: 900
600s
eftps.gov TXT v=spf1 a:mail1.eftps.gov a:mail2.eftps.gov a:mail3.eftps.gov -all 600s
eftps.gov 48 [136 bytes] 302400s

Authority records

Additional records

IP 204.194.124.20 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Wilmington
  • Continent Code
    19809
  • Latitude
    302
  • Longitude
    504
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 204.194.124.20"
    #
    # Use "?" to get help.
    #

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

    NetRange: 204.194.120.0 - 204.194.143.255
    CIDR: 204.194.120.0/21, 204.194.128.0/20
    OriginAS:
    NetName: FDC-CTS-HOLDINGS
    NetHandle: NET-204-194-120-0-1
    Parent: NET-204-0-0-0-0
    NetType: Direct Assignment
    RegDate: 1995-01-07
    Updated: 2012-03-02
    Ref: http://whois.arin.net/rest/net/NET-204-194-120-0-1

    OrgName: First Data Corporation
    OrgId: FDC-63
    Address: 101 Bellevue Parkway
    City: Wilmington
    StateProv: DE
    PostalCode: 19809
    Country: US
    RegDate: 2006-04-04
    Updated: 2012-12-11
    Comment: FDC CTS Holdings
    Ref: http://whois.arin.net/rest/org/FDC-63

    OrgNOCHandle: NESNO-ARIN
    OrgNOCName: NESNOC
    OrgNOCPhone: +1-888-377-8726
    OrgNOCEmail: NESNOC@firstdata.com
    OrgNOCRef: http://whois.arin.net/rest/poc/NESNO-ARIN

    OrgAbuseHandle: FDCAB-ARIN
    OrgAbuseName: FDC-Abuse
    OrgAbusePhone: +1-402-777-3098
    OrgAbuseEmail: IPAdmin@firstdata.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/FDCAB-ARIN

    OrgTechHandle: FDCTE-ARIN
    OrgTechName: FDC-Tech
    OrgTechPhone: +1-402-777-3098
    OrgTechEmail: Peter.Riedener@firstdata.com
    OrgTechRef: http://whois.arin.net/rest/poc/FDCTE-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
  • 14 Errors
  • 12 Warnings
Ratio Text/Html
  • 0.4858672752808989
Message Error
  • Error Line 5, Column 13: there is no attribute "XMLNS"
    <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">

    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 5, Column 63: there is no attribute "XML:LANG"
    <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">

    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 7, Column 73: NET-enabling start-tag requires SHORTTAG YES
    <link rel="StyleSheet" href="/eftps/theme/eftps_v3.css" type="text/css" />

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

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

  • Error Line 7, Column 74: character data is not allowed here
    <link rel="StyleSheet" href="/eftps/theme/eftps_v3.css" type="text/css" />

    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.
  • Warning Line 8, Column 78: NET-enabling start-tag requires SHORTTAG YES
    <link rel="StyleSheet" href="/eftps/theme/navigation_v3.css" type="text/css" />

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

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

  • Warning Line 9, Column 53: NET-enabling start-tag requires SHORTTAG YES
    <link rel="shortcut icon" href="/eftps/favicon.ico" />

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

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

  • Error Line 35, Column 28: 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 85, Column 23: there is no attribute "ROLE"
    <div id="header" role="banner">

    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 86, Column 155: NET-enabling start-tag requires SHORTTAG YES
    …Skip to main page content." border="0"/></a><a href="/eftps/direct/EftpsHome.p…

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

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

  • Warning Line 86, Column 357: NET-enabling start-tag requires SHORTTAG YES
    …) Logo, links to home page" border="0"/></a><a href="/eftps/help/homeGovernmen…

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

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

  • Warning Line 86, Column 581: NET-enabling start-tag requires SHORTTAG YES
    …, links to United States Treasury home page" border="0" id="t_logo"/></a></div>

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

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

  • Error Line 89, Column 31: there is no attribute "ROLE"
    			<ul class="headerNav" role="navigation">	

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 90, Column 43: start tag for "LI" omitted, but its declaration does not permit this
    				<div class="unit size1of7 borderRight">
  • Error Line 95, Column 20: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
                				<li><a href="/eftps/direct/EftpsHome.page" class="navAt">HOME</…

    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 103, Column 17: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
             				<li><a href="/eftps/enrollment/new-enrollment-flow">ENROLLMENT</a>…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 110, Column 19: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
                			<li><a href="/eftps/direct/ProfileMain.page">MY PROFILE</a></li> 

    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 117, Column 19: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
                			<li><a href="/eftps/payments/home">PAYMENTS</a></li>

    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 124, Column 19: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
               				<li><a href="/eftps/direct/Help.page">HELP &amp; INFORMATION</a>…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 131, Column 19: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
                			<li><a href="/eftps/direct/ContactUs.page">CONTACT US</a></li>

    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 140, Column 11: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    							<li><a href="/eftps/login/loginInitial">LOGIN</a></li>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 201, Column 85: NET-enabling start-tag requires SHORTTAG YES
    …c="/eftps/images/home/flag_v2.png" width="631" height="64" border="0" alt="" />

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

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

  • Warning Line 207, Column 119: NET-enabling start-tag requires SHORTTAG YES
    …eftps_v3.png" width="224" height="19" border="0" alt="Welcome to EFTPS&reg;" />

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

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

  • Warning Line 218, Column 268: NET-enabling start-tag requires SHORTTAG YES
    …ny tax due to the Internal Revenue Service (IRS) using this system.<br /><br />

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

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

  • Warning Line 218, Column 274: NET-enabling start-tag requires SHORTTAG YES
    …ny tax due to the Internal Revenue Service (IRS) using this system.<br /><br />

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

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

  • Warning Line 234, Column 86: NET-enabling start-tag requires SHORTTAG YES
    …g height="73" width="76" src="/eftps/images/new2.png"  border="0" alt="New!"/> 

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

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

  • Warning Line 237, Column 205: NET-enabling start-tag requires SHORTTAG YES
    …ax period and settlement dates, which reduces the chance of errors.<br /><br />

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

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

  • Warning Line 237, Column 211: NET-enabling start-tag requires SHORTTAG YES
    …ax period and settlement dates, which reduces the chance of errors.<br /><br />

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

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

Visitor Analysis

Daily Visitor
  • 9.217 visits