Let Symptomfind.com help you diagnose your health symptoms. Find common causes, treatments, tests, diagnoses and more for health conditions such as pregnancy, HIV, diabetes, mono, heart attack and depression. ...

symptomfind.com
  • Domain Name
    symptomfind.com
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #20975
  • Page Size
    22.1 KB
  • Ip Address
    216.34.207.194
  • Heading
    H1: 6, H2: 2, H3: 3, H4: 0, H5: 5, H6: 4
  • Images
    0 GIF, 11 JPG, 1 PNG

Website Meta Analysis

  • Title
    Symptomfind.com: Check Your Medical Symptoms & Find Causes, Tests, Diagnosis & Treatments Options
  • Meta Keyword
  • Meta Description
    Let Symptomfind.com help you diagnose your health symptoms. Find common causes, treatments, tests, diagnoses and more for health conditions such as pregnancy, HIV, diabetes, mono, heart attack and depression.

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    216.34.207.194
  • Domain Age
    5 Years, 1 Months, 15 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Mon, 09 Sep 2013 18:04:38 GMT
  • server: Apache
  • x-frame-options: ALLOW-FROM https://www.optimizely.com
  • content-encoding: gzip
  • vary: User-Agent
  • content-length: 6794
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Domain Administrator
ValueClick, Inc
30699 Russell Ranch Rd
Westlake Village CA 91361
US
email +1.8185323580 Fax: +1.8185754501

Domain Name: symptomfind.com

Registrar Name: Markmonitor.com
Registrar Whois: whois.markmonitor.com
Registrar Homepage: http://www.markmonitor.com

Administrative Contact:
Domain Administrator
ValueClick, Inc
30699 Russell Ranch Rd
Westlake Village CA 91361
US
email +1.8185323580 Fax: +1.8185754501
Technical Contact, Zone Contact:
Domain Administrator
ValueClick, Inc
30699 Russell Ranch Rd
Westlake Village CA 91361
US
email +1.8185323580 Fax: +1.8185754501

Created on..............: 2008-07-22.
Expires on..............: 2014-07-22.
Record last updated on..: 2012-01-09.

Domain servers in listed order:

ns2.mediaplex.com
ns1.mediaplex.com

DNS Analysis


DNS servers
ns2.mediaplex.com [64.70.58.72]
ns1.mediaplex.com [64.158.223.64]


DNS Records

Answer records
symptomfind.com SOA
server: fs1.vclk.net
email: hostmaster@valueclick.com
serial: 2012121101
refresh: 7200
retry: 900
expire: 604800
minimum ttl: 600
172800s
symptomfind.com TXT v=spf1 -all 172800s
symptomfind.com MX
preference: 10
exchange: smtp.vclk.net
172800s
symptomfind.com NS  ns1.mediaplex.com 172800s
symptomfind.com NS  ns2.mediaplex.com 172800s
symptomfind.com A 216.34.207.194 7200s

Authority records

Additional records

IP 216.34.207.194 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 13 Errors
  • 4 Warnings
Ratio Text/Html
  • 0.6181440198159943
Message Error
  • Error Line 12, Column 111: end tag for element "script" which is not open
    …rc="http://files.symptomfind.com/js/minify/jquery@main!20121212.js" /></script>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Warning Line 16, Column 30: ignored marked section in the instance
    <!--[if !ie]><![IGNORE[--><![IGNORE[]]>
  • Warning Line 48, Column 25: character "&" is the first character of a delimiter but occurred as data
    			}else if('' != 'adk' && '' != 'arb'){

    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 48, Column 26: character "&" is the first character of a delimiter but occurred as data
    			}else if('' != 'adk' && '' != 'arb'){

    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 71, Column 8: 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 89, Column 23: an attribute specification must start with a name or name token
    		document.write('<scr' + 'ipt src="' + src + '"></scr' + 'ipt>');

    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 89, Column 23: element "scr" undefined
    		document.write('<scr' + 'ipt src="' + src + '"></scr' + 'ipt>');

    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).
  • Error Line 89, Column 55: delimiter "'" invalid: only S separators and TAGC allowed here
    		document.write('<scr' + 'ipt src="' + src + '"></scr' + 'ipt>');
  • Warning Line 160, Column 70: cannot generate system identifier for general entity "A"
    …f="/health/seasonal-flu-qa/" title="Seasonal Flu Q&A">Seasonal Flu Q&A</a></h2>

    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 160, Column 70: general entity "A" not defined and no default entity
    …f="/health/seasonal-flu-qa/" title="Seasonal Flu Q&A">Seasonal Flu Q&A</a></h2>

    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 160, Column 71: reference not terminated by REFC delimiter
    …f="/health/seasonal-flu-qa/" title="Seasonal Flu Q&A">Seasonal Flu Q&A</a></h2>

    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 160, Column 71: reference to external entity in attribute value
    …f="/health/seasonal-flu-qa/" title="Seasonal Flu Q&A">Seasonal Flu Q&A</a></h2>

    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 160, Column 71: reference to entity "A" for which no system identifier could be generated
    …f="/health/seasonal-flu-qa/" title="Seasonal Flu Q&A">Seasonal Flu Q&A</a></h2>

    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 160, Column 69: entity was defined here
    …f="/health/seasonal-flu-qa/" title="Seasonal Flu Q&A">Seasonal Flu Q&A</a></h2>
  • Warning Line 160, Column 89: reference not terminated by REFC delimiter
    …f="/health/seasonal-flu-qa/" title="Seasonal Flu Q&A">Seasonal Flu Q&A</a></h2>

    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 160, Column 89: reference to entity "A" for which no system identifier could be generated
    …f="/health/seasonal-flu-qa/" title="Seasonal Flu Q&A">Seasonal Flu Q&A</a></h2>

    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 160, Column 69: entity was defined here
    …f="/health/seasonal-flu-qa/" title="Seasonal Flu Q&A">Seasonal Flu Q&A</a></h2>
  • Warning Line 161, Column 79: reference not terminated by REFC delimiter
    		<div class="row1"><a href="/health/seasonal-flu-qa/" title="Seasonal Flu Q&A">

    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 161, Column 79: reference to external entity in attribute value
    		<div class="row1"><a href="/health/seasonal-flu-qa/" title="Seasonal Flu Q&A">

    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 161, Column 79: reference to entity "A" for which no system identifier could be generated
    		<div class="row1"><a href="/health/seasonal-flu-qa/" title="Seasonal Flu Q&A">

    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 160, Column 69: entity was defined here
    …f="/health/seasonal-flu-qa/" title="Seasonal Flu Q&A">Seasonal Flu Q&A</a></h2>
  • Warning Line 162, Column 119: reference not terminated by REFC delimiter
    …l-flu-qa_1359509112.jpg" alt="Seasonal Flu Q&A" width="177" height="100" /></a>

    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 162, Column 119: reference to external entity in attribute value
    …l-flu-qa_1359509112.jpg" alt="Seasonal Flu Q&A" width="177" height="100" /></a>

    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 162, Column 119: reference to entity "A" for which no system identifier could be generated
    …l-flu-qa_1359509112.jpg" alt="Seasonal Flu Q&A" width="177" height="100" /></a>

    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 160, Column 69: entity was defined here
    …f="/health/seasonal-flu-qa/" title="Seasonal Flu Q&A">Seasonal Flu Q&A</a></h2>

Visitor Analysis

Daily Visitor
  • 15.050 visits