bn.com.pe

bn.com.pe

Portal del Banco de la Nación del Peru,Sistema Financiero, Entidades Financieras, Ranking del Sistema Bancario, Grupos Financieros, Off Shore, economía peruana,república del peru, Servicios al público, Instituciones Públicas,Tarjetas de Crédito,Otras Instituciones ,Crédito,Tarjetas,Normativa,Detracciones ...

Domain Name bn.com.pe
Favicon bn.com.pe
Google Page Rank 6
Alexa Rank #24896
Page Size 45.8 KB
Ip Address 200.48.202.43
Heading H1: 1, H2: 1, H3: 9, H4: 3, H5: 0, H6: 0
Images 3 GIF, 3 JPG, 6 PNG

Website Meta Analysis

Title Banco de la Nación
Meta Keyword Banco de la Nación, BN, Multired, Banco Nación, Banco, Nación, Detracciones, Nacional, Home Banking, Peru, Ahorros, créditos, servicios, crédito hipotecario, Noticias, pymes, Gobiernos Locales, Corresponsalía, pagos, tasas, tarjetas, prestamos, cambio, monedas, cronograma de pagos, operaciones en línea
Meta Description Portal del Banco de la Nación del Peru,Sistema Financiero, Entidades Financieras, Ranking del Sistema Bancario, Grupos Financieros, Off Shore, economía peruana,república del peru, Servicios al público, Instituciones Públicas,Tarjetas de Crédito,Otras Instituciones ,Crédito,Tarjetas,Normativa,Detracciones

Technical Analysis

Webserver
Ip Address 200.48.202.43
Domain Age
Javascript Library jquery
Language used HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: private
  • content-type: text/html
  • x-powered-by: ASP.NET
  • date: Mon, 17 Jun 2013 12:21:00 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated. Whois database is provided as a service to the internet
community.

The data is for information purposes only. Red Cientifica Peruana 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 e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes.

The compilation, repackaging, dissemination or other use of this Data is
expressly prohibited.


Domain Information
Query: bn.com.pe
Status: Active
Registrar: NIC .PE
Name Servers:
dns1.unired.net.pe
dns2.unired.net.pe

Registrant:
banco de la nacion

Administrative Contact:
.
email


Technical Analysis


DNS servers
dns1.unired.net.pe [200.37.10.34]
dns2.unired.net.pe [200.37.10.35]


DNS Records

Answer records
bn.com.pe MX
preference: 10
exchange: smtp.bn.com.pe
3600s
bn.com.pe A 200.48.202.43 3600s
bn.com.pe SOA
server: dns1.unired.net.pe
email: hostmaster@unired.net.pe
serial: 2012022300
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 86400
3600s
bn.com.pe NS  dns1.unired.net.pe 3600s
bn.com.pe NS  dns2.unired.net.pe 3600s

Authority records

Additional records
smtp.bn.com.pe A 200.48.202.39 3600s
dns1.unired.net.pe A 200.37.10.34 3600s
dns2.unired.net.pe A 200.37.10.35 3600s

IP 200.48.202.43 Analysis

Country Code : PE
Country Code3 : PER
Country Name : Peru
City : Lima
Continent Code : SA
Latitude : 12.05
Longitude : 77.05


% Joint Whois - whois.lacnic.net
% This server accepts single ASN, IPv4 or IPv6 queries

% LACNIC resource: whois.lacnic.net


% Copyright LACNIC lacnic.net
% The data below is provided for information purposes
% and to assist persons in obtaining information about or
% related to AS and IP numbers registrations
% By submitting a whois query, you agree to use this data
% only for lawful purposes.
% 2013-01-25 18:00:11 (BRST -02:00)

inetnum: 200.48/16
status: allocated
aut-num: N/A
owner: Telefonica del Peru S.A.A.
ownerid: PE-TPSA-LACNIC
responsible: Telefonica del Peru
address: Jorge Basadre, 592, 505
address: L27 - Lima - LI
country: PE
phone: +51 1 2109687 []
owner-c: JOR
tech-c: JOR
abuse-c: JOR
inetrev: 200.48/16
nserver: DNS3.UNIRED.NET.PE
nsstat: 20130122 AA
nslastaa: 20130122
nserver: DNS4.UNIRED.NET.PE
nsstat: 20130122 AA
nslastaa: 20130122
remarks: ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
created: 19990315
changed: 20020131

nic-hdl: JOR
person: System Admin
e-mail: sysadm@UNIRED.NET.PE
address: Jorge Basadre 592, 592, 505
address: L27 - Lima - LI
country: PE
phone: +51 01 2109687 []
created: 20020926
changed: 20030829

% whois.lacnic.net accepts only direct match queries.
% Types of queries are: POCs, ownerid, CIDR blocks, IP
% and AS numbers.

In Page Analysis

Traffic Analysis

Magestic Backlinks

Daily Ranks

Rank Trend

Visitor Trend

Bounce Trend

HTML Analysis

HTML validation
  • 6 Errors
  • 9 Warnings
Ratio Text/Html

0.7186747116389143

Message Error
  • Warning Line 176, Column 85: cannot generate system identifier for general entity "PFL"
    …/0/modulos/JER/JER_Interna.aspx?ARE=0&PFL=1&JER=1312" target="_blank">Vídeo de…

    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 "&" (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 æ 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 176, Column 85: general entity "PFL" not defined and no default entity
    …/0/modulos/JER/JER_Interna.aspx?ARE=0&PFL=1&JER=1312" target="_blank">Vídeo de…

    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 176, Column 88: reference not terminated by REFC delimiter
    …modulos/JER/JER_Interna.aspx?ARE=0&PFL=1&JER=1312" target="_blank">Vídeo de Or…

    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 176, Column 88: reference to external entity in attribute value
    …modulos/JER/JER_Interna.aspx?ARE=0&PFL=1&JER=1312" target="_blank">Vídeo de Or…

    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 '&'.

  • Error Line 176, Column 88: reference to entity "PFL" for which no system identifier could be generated
    …modulos/JER/JER_Interna.aspx?ARE=0&PFL=1&JER=1312" target="_blank">Vídeo de Or…

    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 176, Column 84: entity was defined here
    …e/0/modulos/JER/JER_Interna.aspx?ARE=0&PFL=1&JER=1312" target="_blank">Vídeo d…
  • Warning Line 176, Column 91: cannot generate system identifier for general entity "JER"
    …ulos/JER/JER_Interna.aspx?ARE=0&PFL=1&JER=1312" target="_blank">Vídeo de Orien…

    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 "&" (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 æ 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 176, Column 91: general entity "JER" not defined and no default entity
    …ulos/JER/JER_Interna.aspx?ARE=0&PFL=1&JER=1312" target="_blank">Vídeo de Orien…

    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 176, Column 94: reference not terminated by REFC delimiter
    …s/JER/JER_Interna.aspx?ARE=0&PFL=1&JER=1312" target="_blank">Vídeo de Orientac…

    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 176, Column 94: reference to external entity in attribute value
    …s/JER/JER_Interna.aspx?ARE=0&PFL=1&JER=1312" target="_blank">Vídeo de Orientac…

    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 '&'.

  • Error Line 176, Column 94: reference to entity "JER" for which no system identifier could be generated
    …s/JER/JER_Interna.aspx?ARE=0&PFL=1&JER=1312" target="_blank">Vídeo de Orientac…

    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 176, Column 90: entity was defined here
    …dulos/JER/JER_Interna.aspx?ARE=0&PFL=1&JER=1312" target="_blank">Vídeo de Orie…

Visitor Analysis

Daily Visitor

4.900 visits

Daily Visitor