fictionmania.tv

Fictionmania is a big story archive. Transgender / TV / CD / TG stories, with images too. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 17-09-2013 05:33:00  (update).

Overview Info

  • Domain Name
    fictionmania.tv
  • Favicon
  • Alexa Rank
    #40913
  • Google Page Rank
    PR 4
  • Ip Address
    85.214.56.55
  • Page Size
    4.9 KB
  • Images
    1 GIF, 1 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 2 1 1 0 0

Website Meta Analysis



  • Title
    FictionMania Story Archive
  • Meta Keyword
    TG, CD, TV, Transgender, Crossdressing, Transvestite, Shemale, MtF, FtM, Trans Man, Trans Woman, Trigender, Pangender, Bigender, Agender, Third Gender, Third Sex, Gender Role, Drag Queen, Drag King, Genderqueer
  • Meta Description
    Fictionmania is a big story archive. Transgender / TV / CD / TG stories, with images too.

Technical Analysis



  • Webserver
  • Ip Address
    85.214.56.55
  • Domain Age
    4 Years, 6 Months, 14 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from fictionmania.tv.

HTML Analysis

  • content-type: text/html
  • connection: Close
  • mime-version: 1.0
  • date: Tue, 17 Sep 2013 17:32:57 GMT
  • expires: Tue, 17 Sep 2013 17:32:57 GMT
  • content-length: 4857
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for fictionmania.tv

DNS Analysis


DNS servers
ns.stratoserver.net [81.169.163.40]
ns2.stratoserver.net [81.169.148.41]


DNS Records

Answer records
fictionmania.tv SOA
server: ns.stratoserver.net
email: hostmaster@stratoserver.net
serial: 2009112901
refresh: 10000
retry: 14400
expire: 604800
minimum ttl: 1800
1800s
fictionmania.tv NS  ns.stratoserver.net 1800s
fictionmania.tv NS  ns2.stratoserver.net 1800s
fictionmania.tv A 85.214.56.55 1800s
fictionmania.tv MX
preference: 10
exchange: fictionmania.tv
1800s

Authority records

Additional records
ns.stratoserver.net A 81.169.163.40 1800s
ns.stratoserver.net 28 [16 bytes] 1800s
ns2.stratoserver.net A 81.169.148.41 1800s
ns2.stratoserver.net 28 [16 bytes] 1800s

IP 85.214.56.55 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 7 Errors
  • 1 Warnings
Ratio Text/Html
  • 0.42361111111111116
Message Error
  • Error Line 4, Column 3: unknown declaration type "HAS_WEBDNA_TAGS"
    <!HAS_WEBDNA_TAGS> 

    This error may appear if you are using a bad syntax for your comments, such as "<!invalid comment>" The proper syntax for comments is <!-- your comment here -->.

  • Warning Line 51, Column 69: cannot generate system identifier for general entity "ID"
    …tique.com/index.asp?PageAction=Custom&ID=52"><img style="border-width:0pt;" al…

    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 51, Column 69: general entity "ID" not defined and no default entity
    …tique.com/index.asp?PageAction=Custom&ID=52"><img style="border-width:0pt;" al…

    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.

  • Error Line 51, Column 71: reference to entity "ID" for which no system identifier could be generated
    …que.com/index.asp?PageAction=Custom&ID=52"><img style="border-width:0pt;" alt=…

    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 51, Column 68: entity was defined here
    …utique.com/index.asp?PageAction=Custom&ID=52"><img style="border-width:0pt;" a…
  • Error Line 53, Column 71: reference to entity "ID" for which no system identifier could be generated
    …que.com/index.asp?PageAction=Custom&ID=52"><img style="border-width:0pt;" alt=…

    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 51, Column 68: entity was defined here
    …utique.com/index.asp?PageAction=Custom&ID=52"><img style="border-width:0pt;" a…
  • Error Line 55, Column 119: reference to entity "ID" for which no system identifier could be generated
    …lamourboutique.com/index.asp?PageAction=Custom&ID=52">Glamour Boutique</a></h3>

    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 51, Column 68: entity was defined here
    …utique.com/index.asp?PageAction=Custom&ID=52"><img style="border-width:0pt;" a…
  • Error Line 69, Column 15: end tag for element "CENTER" which is not open
    </div></center>

    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.

  • Error Line 74, Column 91: end tag for element "CENTER" which is not open
    …nter"><b>By accepting this agreement, I certify the following:</b></p></center>

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

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

Visitor Analysis

Daily Visitor
  • 2.333 visits

In Page Analysis