Analysis report on IP address: 199.212.0.63

199.212.0.63
Generated on
19 Apr 2021 07:05
Duration of the analysis
11.4s
Share

Score 93%
A
DNS
A
IP
A
MAIL
-
WEB
A

Resume

BIND version is hidden

Dns version is visible for ns3.lacnic.net with IP 200.3.13.14 : 9.16.4.

DNS

Dns servers for 0.212.199.in-addr.arpa

199.212.0.63 was detected as ipv4

Query informations

Server
d.root-servers.net
[ 199.7.91.13 ]
Duration
9 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
a.in-addr-servers.arpa
[ 199.180.182.53 ]
Duration
144 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
b.in-addr-servers.arpa
[ 199.253.183.183 ]
Duration
45 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
c.in-addr-servers.arpa
[ 196.216.169.10 ]
Duration
183 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
d.in-addr-servers.arpa
[ 200.10.60.53 ]
Duration
247 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
e.in-addr-servers.arpa
[ 203.119.86.101 ]
Duration
296 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
f.in-addr-servers.arpa
[ 193.0.9.1 ]
Duration
24 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
arin.authdns.ripe.net
[ 193.0.9.10 ]
Duration
14 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
r.arin.net
[ 199.180.180.63 ]
Duration
292 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
u.arin.net
[ 204.61.216.50 ]
Duration
15 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
x.arin.net
[ 199.180.180.63 ]
Duration
153 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
y.arin.net
[ 192.82.134.30 ]
Duration
16 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
z.arin.net
[ 199.212.0.63 ]
Duration
97 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
arin.authdns.ripe.net
[ 193.0.9.10 ]
Duration
15 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns1.arin.net
[ 199.212.0.108 ]
Duration
82 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns2.arin.net
[ 199.71.0.108 ]
Duration
149 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns3.arin.net
[ 199.5.26.108 ]
Duration
139 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns3.lacnic.net
[ 200.3.13.14 ]
Duration
196 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns4.apnic.net
[ 202.12.31.53 ]
Duration
150 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0
DNSSEC analysis not possible on an IP

BIND version is hidden

Dns version is visible for ns3.lacnic.net with IP 200.3.13.14 : 9.16.4.

The Bind version should not be visible otherwise it will be possible to search for potential security vulnerabilities of the version.

0.722s

Domain have at least 2 DNS servers

Passed

In order for the availability rate of DNS servers to be at its highest, it is vital and recommended by the RFC to have at least 2 servers.

RFC

0.000s

All Dns servers are responding

Passed

Every DNS servers should be accessible and accept public query.

0.005s

All servers return success

Passed

It's important that all servers returned a "success" code.

0.005s

Responses are not CNAME or A

Passed

The answers should not be a CNAME or A type.

RFC

0.005s

DNS servers IP are differents

Passed

IPs for DNS servers must be different in order to have high availability.

0.000s

DNS servers IP are in different class C

Passed

The class C of each IP must be different so that the servers are not found on the same bay and therefore there is a risk of unavailability.

RFC

0.000s

SOA are synchronized

Passed

The SOA answered by the DNS servers must be identical for each servers. The most important information is the master server and the contact email address.

0.000s

SOA email is valid

Passed

An email address must respect some conditions to be valid, accordding to the RFC 5322.

RFC

0.000s

SOA refresh is valid

Passed

The refresh value be must between 1200 and 43200.

RFC

0.000s

SOA retry, refresh and expire values are correct

Passed

The Retry, Refresh and Expire values musth follow this path : retry < refresh < expire.

RFC

0.000s

DNS servers are not open relay

Passed

DNS resolvers that allow queries from all IP addresses and are exposed to the Internet can be attacked and used to conduct Denial of Service (DoS) attacks on behalf of the hacker.

0.728s

Transfer zone is disable

Passed

An attacker can use a zone transfer that contains a malicious code or an inappropriate format that crashes a DNS server vulnerable to this type of attack, which results in a DoS that destabilizes the DNS services. It is possible to test it manually with this commands: #host -T axfr or #dig axfr.

documentation

2.244s

Recursive query is disable

Passed

Having a dns server that allow recursive queries is a security risk, DDOS attack can be performed.

RFC documentation documentation

0.719s

DNS servers IP are not private

Passed

It is strictly forbidden to have private IP in DNS

documentation

0.000s

DNS servers are synchronized

Skipped

The synchronization of the DNS servers must be perfect in order to avoid any dns resolution error. The servers must therefore give the same answer when asked "what are the DNS servers for the domain?".

0.000s

Ip

Informations

Ip
199.212.0.63
Type
ipv4
Reverse
z.arin.net
ARPA
63.0.212.199.in-addr.arpa
Class C
199.212.0.0/24
ASN
393225 ARIN-PFS-IAD
Organisation
 
Maintainer
 

Reputation

Blacklists
Ip
Whois server
whois.arin.net
Raw data
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2021, American Registry for Internet Numbers, Ltd.
#


NetRange:       199.212.0.0 - 199.212.0.255
CIDR:           199.212.0.0/24
NetName:        ARIN-PFS-IAD
NetHandle:      NET-199-212-0-0-1
Parent:         NET199 (NET-199-0-0-0-0)
NetType:        Direct Assignment
OriginAS:       AS393225
Organization:   ARIN Operations (ARINOPS)
RegDate:        2008-06-10
Updated:        2015-07-15
Ref:            https://rdap.arin.net/registry/ip/199.212.0.0


OrgName:        ARIN Operations
OrgId:          ARINOPS
Address:        PO Box 232290
City:           Centreville
StateProv:      VA
PostalCode:     20120
Country:        US
RegDate:        2012-09-07
Updated:        2020-06-16
Ref:            https://rdap.arin.net/registry/entity/ARINOPS


OrgAbuseHandle: AOA4-ARIN
OrgAbuseName:   ARIN Operations Abuse
OrgAbusePhone:  +1-703-227-0660 
OrgAbuseEmail:  dXaJh3k= [at] arin.net
OrgAbuseRef:    https://rdap.arin.net/registry/entity/AOA4-ARIN

OrgTechHandle: TOSCA5-ARIN
OrgTechName:   Toscano, Pete 
OrgTechPhone:  +1-703-942-9542 
OrgTechEmail:  hHmIeQ== [at] arin.net
OrgTechRef:    https://rdap.arin.net/registry/entity/TOSCA5-ARIN

OrgDNSHandle: JEFFE114-ARIN
OrgDNSName:   Jeffers, David 
OrgDNSPhone:  +1-703-227-0660 
OrgDNSEmail:  eHWKfXg= [at] arin.net
OrgDNSRef:    https://rdap.arin.net/registry/entity/JEFFE114-ARIN

OrgNOCHandle: JEFFE114-ARIN
OrgNOCName:   Jeffers, David 
OrgNOCPhone:  +1-703-227-0660 
OrgNOCEmail:  eHWKfXg= [at] arin.net
OrgNOCRef:    https://rdap.arin.net/registry/entity/JEFFE114-ARIN

OrgTechHandle: FORST20-ARIN
OrgTechName:   Forster, Reggie 
OrgTechPhone:  +1-703-227-0660 
OrgTechEmail:  hnqDhoeIeYY= [at] arin.net
OrgTechRef:    https://rdap.arin.net/registry/entity/FORST20-ARIN

OrgTechHandle: MJO282-ARIN
OrgTechName:   O'Neill, Michael J
OrgTechPhone:  +1-703-227-0660 
OrgTechEmail:  gX6D [at] arin.net
OrgTechRef:    https://rdap.arin.net/registry/entity/MJO282-ARIN

OrgNOCHandle: MJO282-ARIN
OrgNOCName:   O'Neill, Michael J
OrgNOCPhone:  +1-703-227-0660 
OrgNOCEmail:  gX6D [at] arin.net
OrgNOCRef:    https://rdap.arin.net/registry/entity/MJO282-ARIN


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2021, American Registry for Internet Numbers, Ltd.
#

Blacklists

RFC Ignorant
Rbl Jp
RblDns
Sorbs
Spam Eating Monkey
SpamHaus
SuRbl
Support Intelligence
Swinog
UriBl

Ip is not blacklisted

SpamHaus has blacklisted your domain/IP.

An ip must not be blacklisted or it will be penalized for referencing and deliverability of emails.

0.001s

Mail

There is no mail server. Please test z.arin.net.

Name
z.arin.net
IP
199.212.0.63
Accessible
Autodiscover analysis not possible on an IP

MX IPs have reverse

Passed

When a sending server makes a connection to the recipient server, the recipient server notes the sending IP address and performs a reverse lookup, called a PTR lookup, named after the type of DNS record used. If the result of the reverse lookup matches the result of a forward DNS Lookup, then it's much more likely that the message is legitimate. If the IP address doesn't match, it's much more likely that the sending address was spoofed and therefore much more likely that it's unwanted and could be considered spam.

documentation

0.000s

MX servers are accessibles

Skipped

Smtp servers that are listed in DNS area must be accessible, otherwise, there is a risk that emails may be lost

0.000s

HELO command is accepted

Skipped

According to the RFC 2181, smtp server should accept HELO command

RFC

0.000s

EHLO command is accepted

Skipped

According to the RFC 2181, smtp server should accept EHLO command

RFC

0.000s

STARTTLS command is accepted

Skipped

STARTTLS turns an unencrypted connection into a secure connection. Note: You can use a service like altospam to solve this problem. Click on the link below to learn more

0.000s

EXPN command is refused

Skipped

EXPN command is now considered to be a security risk, spammers being able to harvest valid e-mail addresses via each mailing list.

0.000s

VRFY command is refused

Skipped

As the EXPN command, VRFY is used by spammers to verify an address.

0.000s

MX servers are not open relay

Skipped

If a server is open relay, there is a risk that spammers use your server to send illegitimate mail.

0.000s

MX servers accept abuse@ address

Skipped

According to the RFC 2142, SMTP server should accept abuse@yourDomain as a recipient.

RFC

0.000s

MX servers accept postmaster@ address

Skipped

According to the RFC 5321, SMTP server should accept postmaster@yourDomain as a recipient.

RFC

0.000s

Banner return 2xx or 4xx code

Skipped

The banner must return (2xx) a valid (4xx) or temporary code.

0.000s

Banner return server name

Skipped

Banner must contain the name of the server

0.000s

SMTP server type is hidden

Skipped

There is a risk to display the type and the version of the server, because people can find a breach for a specific version and use it

0.000s

Web

There is no web server. Please test z.arin.net.

Url
http://199.212.0.63/
Reachable
No
Url
https://199.212.0.63/
Reachable
No

HTTP port (80) is open

Skipped

This test verifies the presence of a website for the given IP or domain. Then scans port 80.
If the domain or IP is pointing to a website then port 80 must be open so that it can be accessed from a browser.
Otherwise port 80 must be closed.

0.000s

HTTPS port (443) is open

Skipped

This test verifies the presence of a website for the given IP or domain. Then scans port 443.
If the domain or IP is pointing to a website then port 443 must be open so that it can be accessed from a browser.
Otherwise port 443 must be closed.

0.000s

Web server version is hidden

Skipped

To avoid giving details to malicious people, the version of the server should not be visible.

0.000s

Web application technology is hidden

Skipped

To avoid giving details to malicious people, the technology that supports the application should not be visible.

0.000s

Cookies are secure

Skipped

Using "HttpOnly" instruction prevents someone to access to cookies via Javascript. The secure flag will allow you to prevent a cookie from ever being communicated in simple HTTP. (RFC 6265 section 8.3)

RFC

0.000s

X-XSS-Protection header is present

Skipped

The HTTP X-XSS-Protection response header is a feature of Internet Explorer, Chrome and Safari that stops pages from loading when they detect reflected cross-site scripting (XSS) attacks.

documentation

0.000s

Content Security Policy header is present

Skipped

The HTTP Content-Security-Policy response header allows web site administrators to control resources the user agent is allowed to load for a given page. With a few exceptions, policies mostly involve specifying server origins and script endpoints. This helps guard against cross-site scripting attacks (XSS).

documentation

0.000s

Content Type Options header is present

Skipped

The only defined value, "nosniff", prevents Internet Explorer from MIME-sniffing a response away from the declared content-type. This also applies to Google Chrome, when downloading extensions.

0.000s