Analysis report on domain: whois.arin.net favicon

whois.arin.net has no website

Generated on
12 Jun 2021 10:40
Duration of the analysis
91.3s
Share

Score 86%
B
DNS
B
DOMAIN
A
MAIL
A
WEB
B

Resume

All Dns servers are responding

One or more servers are not responding (timeout, refused, ...)

DNS servers are same in dns tree and whois

The whois name servers are not the same as the name servers from a dns query.

Whois return: ns1.arin.net, ns2.arin.net, ns3.arin.net, u.arin.net
DNS tree return: ns1.arin.net, ns3.arin.net, u.arin.net

Web server version is hidden

Version 2.4.6 has been found.

X-XSS-Protection header is present

The X-XSS-Protection header was not found.

Content Type Options header is present

The X-Content-Type-Options header was not found.

Content Security Policy header is present

The Content-Security-Policy header was not found.

DNS

Dns servers for arin.net

whois.arin.net was detected as host

Possible problem in Dns Tree

We have detected the following error on one or more server(s).
Consult Tree for more details.

  • Refuse to respond or is in timeout state.

Host informations

Ips
 
Cname
-

Query informations

Server
g.root-servers.net
[ 192.112.36.4 ]
Duration
84 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
a.gtld-servers.net
[ 192.5.6.30 ]
Duration
60 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
b.gtld-servers.net
[ 192.33.14.30 ]
Duration
20 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
c.gtld-servers.net
[ 192.26.92.30 ]
Duration
54 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
d.gtld-servers.net
[ 192.31.80.30 ]
Duration
63 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
e.gtld-servers.net
[ 192.12.94.30 ]
Duration
61 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
f.gtld-servers.net
[ 192.35.51.30 ]
Duration
28 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
g.gtld-servers.net
[ 192.42.93.30 ]
Duration
29 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
h.gtld-servers.net
[ 192.54.112.30 ]
Duration
29 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
i.gtld-servers.net
[ 192.43.172.30 ]
Duration
27 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
j.gtld-servers.net
[ 192.48.79.30 ]
Duration
31 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
k.gtld-servers.net
[ 192.52.178.30 ]
Duration
19 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
l.gtld-servers.net
[ 192.41.162.30 ]
Duration
17 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
m.gtld-servers.net
[ 192.55.83.30 ]
Duration
18 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

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
5008 ms
Type
timeout
Headers
RCODE : - AA : - TC : -

Délai d'expiration du serveur

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
u.arin.net
[ 204.61.216.50 ]
Duration
2 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Name servers

A and AAAA fields

IPv4
199.5.26.46
TTL
300 (5 minutes )
IPv4
199.71.0.46
TTL
300 (5 minutes )
IPv4
199.212.0.46
TTL
300 (5 minutes )
IPv6
2001:500:31:0:0:0:0:46
TTL
300 (5 minutes )
IPv6
2001:500:13:0:0:0:0:46
TTL
300 (5 minutes )
IPv6
2001:500:a9:0:0:0:0:46
TTL
300 (5 minutes )

SOA

From
u.arin.net
Master server
ns1.arin.net
TTL
3600 (1 hour)
Contact
dn2CeA==@arin.net
Serial
2017082205
Refresh
10800 (3 hours)
Retry
600 (10 minutes)
Expire
1209600 (2 weeks)
Minimum
3600 (1 hour)

RRSIG

Numbers of Labels
2
Created
11 Jun 2021 11:00
Expire
25 Jun 2021 12:00
Algorithme
8 (RSA/SHA-256)
Orig TTL
43200 (12 hours)
TTL
3600 (1 hour)
signature Name
arin.net
signature
bkO2ilGdrPi/3p4Ewe4AeA3M2JPyfRvcMJdyloEHspTx6vMiPbmAG6L3r00dIIPdOy1FoeTJumwpET4x7Luybf03qNTKpAgaBO+XM0IoeT0oonht6R6CvAQaodhBBXUVDHiaUGioQKX+WsEtuOk9Q9YcDhKDtKZiBK0J4VAo6SsDxlIJMFXYwcNxfiXbkjSe94Vn/k+nLigcB5pgr0ei2KD9qHXMaxH+C1/nC1rGk1rA7VDxBrom2mZV/SFuTBs1sIsStl4YW0+hfdIDKy/FzgipMtsTrvcxqJh4t2I2gQNN8HPubW9TBsRiksENgr+NdSBkv52V5QAO4BlmzUCObA==

All Dns servers are responding

One or more servers are not responding (timeout, refused, ...)

Every DNS servers should be accessible and accept public query.

0.009s

BIND version is hidden

Passed

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

0.233s

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 servers return success

Passed

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

0.008s

Responses are not CNAME or A

Passed

The answers should not be a CNAME or A type.

RFC

0.008s

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.236s

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

0.732s

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.232s

DNS servers IP are not private

Passed

It is strictly forbidden to have private IP in DNS

documentation

0.000s

Same MX are returned

Passed

It is extremely important that each DNS return the same MX records in order to avoid contacting an SMTP server that no longer exists.

0.232s

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

Domain

Whois

Registrar
GKG.Net, Inc.
Owner
-
Created at
19 Dec 1996
Changed at
01 Jun 2021
Expires at
13 Jun 2024

Reputation

Google Safe Browsing
Web of trust
Blacklists
Virus Total
Domain
Whois server
whois.gkg.net
Created at
19 Dec 1996
Changed at
01 Jun 2021
Expires at
13 Jun 2024
Name servers
Registrar
Id
93
Name
GKG.Net, Inc.
Phone
-
Email
Url
-

Google Safe Browsing

Status

Web of Trust

Status

Blacklists

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

Virus Total

Detection ratio
0 / 88

Scans

ADMINUSLabs
AICC (MONITORAPP)
AegisLab WebGuard
AlienVault
Antiy-AVL
Armis
Artists Against 419
Avira
BADWARE.INFO
Baidu-International
Bfore.Ai PreCrime
BitDefender
BlockList
Blueliv
CINS Army
CLEAN MX
CMC Threat Intelligence
CRDF
Certego
Cisco Talos IP Blacklist
Comodo Valkyrie Verdict
CyRadar
CyberCrime
Cyren
DNS8
Dr.Web
ESET
EmergingThreats
Emsisoft
EonScope
Feodo Tracker
Forcepoint ThreatSeeker
Fortinet
FraudScore
G-Data
Google Safebrowsing
GreenSnow
Hoplite Industries
IPsum
K7AntiVirus
Kaspersky
MalBeacon
MalSilo
MalwareDomainList
MalwarePatrol
Malwared
Nucleon
OpenPhish
PREBYTES
Phishing Database
Phishtank
Quick Heal
Quttera
Rising
SCUMWARE.org
Sangfor
Scantitan
SecureBrain
Sophos
Spam404
Spamhaus
StopForumSpam
Sucuri SiteCheck
Tencent
ThreatHive
Threatsourcing
Trustwave
URLhaus
VX Vault
Virusdie External Site Scan
Web Security Guard
Webroot
Yandex Safebrowsing
ZeroCERT
alphaMountain.ai
benkow.cc
desenmascara.me
malwares.com URL checker
securolytics
zvelo
AutoShun
Cyan
Lumu
Netcraft
NotMining
PhishLabs
SafeToOpen
StopBadware

DNS servers are same in dns tree and whois

The whois name servers are not the same as the name servers from a dns query.

Whois return: ns1.arin.net, ns2.arin.net, ns3.arin.net, u.arin.net
DNS tree return: ns1.arin.net, ns3.arin.net, u.arin.net

The dns servers given in the domain whois must be the same as those returned by a dns resolution request.

0.000s

Domain is not blacklisted

Passed

A domain must not be blacklisted or it will be penalized for referencing and deliverability of emails.

0.000s

Domain is not listed in Google Safe Browsing

Passed

Google safe browsing categorizes a domain as bad if something suspicious is detected.

0.000s

Domain is not listed in VirusTotal

Passed

Virus Total analyze your domain or IP address with 66 antivirus.

0.000s

Domain have good reputation on Web of Trust

Passed

Web Of Trust rates thousands of websites and find threats if they exist.

0.000s

Mail

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

Name
whois.arin.net
IP
199.5.26.46
Accessible
Name
whois.arin.net
IP
199.71.0.46
Accessible
Name
whois.arin.net
IP
199.212.0.46
Accessible

Autodiscover not configured

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

Website

Url
https://whois.arin.net/ui/
Https
Title
Whois-RWS
Description
First paragraph
Enter a query into the "Search WHOISRWS" box in the upper right corner of this page. By using this service, you are agreeing to the Whois Terms of Use. This is a RESTful web service for Whois data contained within ARIN's registration database. Documentation on the API can be found on the Whois-RWS API Documentation page. By using the ARIN Whois service, you are agreeing to the Whois Terms of Use © Copyright 1997 - 2019, American Registry for Internet Numbers, Ltd.
Url
http://whois.arin.net/
Redirect to
http://whois.arin.net/ui/
Redirect code
302 - found

Headers

  • Connection: close
  • Content-Length: 209
  • Content-Type: text/html; charset=iso-8859-1
  • Date: Sat, 12 Jun 2021 10:41:52 GMT
  • Location: http://whois.arin.net/ui/
  • Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips
Url
http://whois.arin.net/ui/
Title
Whois-RWS
Description
Response time
0.294 second
Server
apache (version 2.4.6)
Powered by
Unknown
Encoding
utf-8
HSTS

Headers

  • Access-Control-Allow-Origin: *
  • Cache-Control: no-cache
  • Connection: close
  • Content-Length: 5731
  • Content-Type: text/html;charset=UTF-8
  • Date: Sat, 12 Jun 2021 10:41:52 GMT
  • Pragma: no-cache
  • Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips
Url
https://whois.arin.net/
Redirect to
https://whois.arin.net/ui/
Redirect code
302 - found

Headers

  • Connection: close
  • Content-Type: text/html; charset=iso-8859-1
  • Date: Sat, 12 Jun 2021 10:41:53 GMT
  • Location: https://whois.arin.net/ui/
  • Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips
  • Transfer-Encoding: chunked
Url
https://whois.arin.net/ui/
Title
Whois-RWS
Description
Response time
0.337 second
Server
apache (version 2.4.6)
Powered by
Unknown
Encoding
utf-8
HSTS

Headers

  • Access-Control-Allow-Origin: *
  • Cache-Control: no-cache
  • Connection: close
  • Content-Type: text/html;charset=UTF-8
  • Date: Sat, 12 Jun 2021 10:41:53 GMT
  • Pragma: no-cache
  • Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips
  • Transfer-Encoding: chunked

Web server version is hidden

Version 2.4.6 has been found.

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

0.000s

X-XSS-Protection header is present

The X-XSS-Protection header was not found.

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 Type Options header is present

The X-Content-Type-Options header was not found.

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.

RFC

0.000s

Content Security Policy header is present

The Content-Security-Policy header was not found.

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

Domain have "A" field

Passed

The domain must have an A field in order for the website to be accessible.

0.000s

Domain have "AAAA" field

Passed

It is highly recommended to have an IPv6 for the website.

0.000s

HTTP port (80) is open

Passed

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

Passed

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 application technology is hidden

Passed

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

0.000s

Host "www" have "A" field

Skipped

WWW host is not required for a website, but it's better to have one.

0.000s

Host "www" have "AAAA" field

Skipped

If you configure a WWW host for your website, it is recommended to have an IPv6.

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