Analysis report on IP address: 192.231.225.2

192.231.225.2 has no website

Generated on
10 Sep 2021 13:37
Duration of the analysis
109.6s
Share

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

Congratulation

Your domain is really well configured

DNS

Dns servers for 225.231.192.in-addr.arpa

192.231.225.2 was detected as ipv4

Possible problem in Dns Tree

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

  • Unknown error
  • Refuse to respond or is in timeout state.

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

Server
arin.authdns.ripe.net
[ 193.0.9.10 ]
Duration
1602 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

Server
ns.tfm.com
[ 104.168.202.181 ]
Duration
149 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns1.tfm.com
[ 174.138.177.151 ]
Duration
89 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Le serveur refuse de répondre à la requête de type dns.

Response

Query informations

Server
ns2.tfm.com
[ 45.77.6.26 ]
Duration
152 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Le serveur refuse de répondre à la requête de type dns.

Response

Query informations

Server
ns.tfm.com
[ 104.168.202.181 ]
Duration
147 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns1.tfm.com
[ 174.138.177.151 ]
Duration
77 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Le serveur refuse de répondre à la requête de type dns.

Response

Query informations

Server
ns2.tfm.com
[ 45.77.6.26 ]
Duration
152 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Le serveur refuse de répondre à la requête de type dns.

Response

Query informations

Server
ns.tfm.com
[ 104.168.202.181 ]
Duration
147 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns1.tfm.com
[ 174.138.177.151 ]
Duration
77 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Le serveur refuse de répondre à la requête de type dns.

Response

Query informations

Server
ns2.tfm.com
[ 45.77.6.26 ]
Duration
152 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Le serveur refuse de répondre à la requête de type dns.

Response

Query informations

Server
ns.tfm.com
[ 104.168.202.181 ]
Duration
147 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns1.tfm.com
[ 174.138.177.151 ]
Duration
77 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Le serveur refuse de répondre à la requête de type dns.

Response

Query informations

Server
ns2.tfm.com
[ 45.77.6.26 ]
Duration
152 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Le serveur refuse de répondre à la requête de type dns.

Response

DNSSEC analysis not possible on an IP

Ip

Informations

Ip
192.231.225.2
Type
ipv4
Reverse
www.tfm.net
ARPA
2.225.231.192.in-addr.arpa
Class C
192.231.225.0/24
ASN
10488 TFM-ASN
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:       192.231.224.0 - 192.231.229.255
CIDR:           192.231.228.0/23, 192.231.224.0/22
NetName:        NETBLK-TFM
NetHandle:      NET-192-231-224-0-1
Parent:         NET192 (NET-192-0-0-0-0)
NetType:        Direct Assignment
OriginAS:       
Organization:   TFM Associates, Ltd. (TAL-1)
RegDate:        1992-10-22
Updated:        2020-09-22
Ref:            https://rdap.arin.net/registry/ip/192.231.224.0


OrgName:        TFM Associates, Ltd.
OrgId:          TAL-1
Address:        P.O. Box 1244
City:           Eugene
StateProv:      OR
PostalCode:     97440-1244
Country:        US
RegDate:        1992-10-22
Updated:        2011-09-24
Ref:            https://rdap.arin.net/registry/entity/TAL-1


OrgTechHandle: SD81-ARIN
OrgTechName:   Diercouff, Stephen 
OrgTechPhone:  +1-541-461-8928 
OrgTechEmail:  h3t4 [at] tfm.net
OrgTechRef:    https://rdap.arin.net/registry/entity/SD81-ARIN

OrgAbuseHandle: SD81-ARIN
OrgAbuseName:   Diercouff, Stephen 
OrgAbusePhone:  +1-541-461-8928 
OrgAbuseEmail:  h3t4 [at] tfm.net
OrgAbuseRef:    https://rdap.arin.net/registry/entity/SD81-ARIN

RTechHandle: SD81-ARIN
RTechName:   Diercouff, Stephen 
RTechPhone:  +1-541-461-8928 
RTechEmail:  h3t4 [at] tfm.net
RTechRef:    https://rdap.arin.net/registry/entity/SD81-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

Passed

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

0.000s

Mail

There is no mail server. Please test www.tfm.net.

Name
www.tfm.net
IP
192.231.225.2
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 www.tfm.net.

Url
http://192.231.225.2/
Timeout
Yes
Url
https://192.231.225.2/
Timeout
Yes

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