Analysis report on IP address: 67.231.158.194

67.231.158.194 has no website

Generated on
13 Oct 2021 18:22
Duration of the analysis
16.7s
Share

Score 89%
B
DNS
-
IP
A
MAIL
A
WEB
B

Resume

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.

HTTP port (80) is open

The http port is close while there is a website.

Content Security Policy header is present

The Content-Security-Policy header was not found.

DNS

Dns servers for 158.231.67.in-addr.arpa

67.231.158.194 was detected as ipv4

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.

Query informations

Server
a.root-servers.net
[ 198.41.0.4 ]
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
141 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
5008 ms
Type
timeout
Headers
RCODE : - AA : - TC : -

Server timeout

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

Server
r.arin.net
[ 199.180.180.63 ]
Duration
157 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
154 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
y.arin.net
[ 192.82.134.30 ]
Duration
35 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
ns1.proofpoint.com
[ 208.84.67.208 ]
Duration
95 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns1.proofpoint.us
[ 208.84.67.208 ]
Duration
95 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns3.proofpoint.com
[ 208.84.66.208 ]
Duration
149 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns3.proofpoint.us
[ 208.84.66.208 ]
Duration
149 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
pdns99.ultradns.biz
[ 156.154.66.99 ]
Duration
3 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
pdns99.ultradns.com
[ 156.154.64.99 ]
Duration
3 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
pdns99.ultradns.net
[ 156.154.65.99 ]
Duration
12 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
pdns99.ultradns.org
[ 156.154.67.99 ]
Duration
21 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0
DNSSEC analysis not possible on an IP

Ip

Informations

Ip
67.231.158.194
Type
ipv4
Reverse
mx0c-001b5501.pphosted.com
ARPA
194.158.231.67.in-addr.arpa
Class C
67.231.158.0/24
ASN
26211 PROOFPOINT-ASN-US-WEST
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:       67.231.144.0 - 67.231.159.255
CIDR:           67.231.144.0/20
NetName:        PROOFPOINT-NET-NORTH-AMERICA
NetHandle:      NET-67-231-144-0-1
Parent:         NET67 (NET-67-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       AS22843, AS13916, AS26211
Organization:   Proofpoint, Inc. (PROOF)
RegDate:        2009-05-20
Updated:        2020-05-29
Ref:            https://rdap.arin.net/registry/ip/67.231.144.0


OrgName:        Proofpoint, Inc.
OrgId:          PROOF
Address:        925 W Maude Ave
City:           Sunnyvale
StateProv:      CA
PostalCode:     94085
Country:        US
RegDate:        2007-10-16
Updated:        2021-06-15
Ref:            https://rdap.arin.net/registry/entity/PROOF


OrgTechHandle: NETWO2061-ARIN
OrgTechName:   Network Operations
OrgTechPhone:  +1-801-748-4444 
OrgTechEmail:  dYZ9gkGBdYJ1e3mBeYKI [at] proofpoint.com
OrgTechRef:    https://rdap.arin.net/registry/entity/NETWO2061-ARIN

OrgAbuseHandle: PAA19-ARIN
OrgAbuseName:   Proofpoint ARIN Abuse
OrgAbusePhone:  +1-801-748-4494 
OrgAbuseEmail:  dXaJh3k= [at] proofpoint.com
OrgAbuseRef:    https://rdap.arin.net/registry/entity/PAA19-ARIN

RNOCHandle: NETWO2061-ARIN
RNOCName:   Network Operations
RNOCPhone:  +1-801-748-4444 
RNOCEmail:  dYZ9gkGBdYJ1e3mBeYKI [at] proofpoint.com
RNOCRef:    https://rdap.arin.net/registry/entity/NETWO2061-ARIN

RAbuseHandle: NETWO2061-ARIN
RAbuseName:   Network Operations
RAbusePhone:  +1-801-748-4444 
RAbuseEmail:  dYZ9gkGBdYJ1e3mBeYKI [at] proofpoint.com
RAbuseRef:    https://rdap.arin.net/registry/entity/NETWO2061-ARIN

RTechHandle: NETWO2061-ARIN
RTechName:   Network Operations
RTechPhone:  +1-801-748-4444 
RTechEmail:  dYZ9gkGBdYJ1e3mBeYKI [at] proofpoint.com
RTechRef:    https://rdap.arin.net/registry/entity/NETWO2061-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

Mail servers

Name
mx0c-001b5501.pphosted.com
IP
67.231.158.194
Banner
220 mx0c-001b5501.pphosted.com ESMTP mfa-m0078369
Name
mx0c-001b5501.pphosted.com
IP
67.231.158.194
Banner
220 mx0c-001b5501.pphosted.com ESMTP mfa-m0078369
Starttls
yes
Dane
no
Mail size
0 Bytes
Expn
no
Vrfy
no

Smtp simulation

Connection to mx0c-001b5501.pphosted.com ...
220 mx0c-001b5501.pphosted.com ESMTP mfa-m0078369
HELO domain.com
250 mx0c-001b5501.pphosted.com Hello ns.tools [195.154.82.101], pleased to meet you
EHLO domain.com
250-mx0c-001b5501.pphosted.com Hello ns.tools [195.154.82.101], pleased to meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250 STARTTLS
QUIT
221 2.0.0 mx0c-001b5501.pphosted.com Closing connection
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

HELO command is accepted

Passed

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

RFC

0.000s

EHLO command is accepted

Passed

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

RFC

0.000s

STARTTLS command is accepted

Passed

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

Passed

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

Passed

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

0.000s

MX servers are not open relay

Passed

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

0.689s

Banner return 2xx or 4xx code

Passed

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

0.000s

Banner return server name

Passed

Banner must contain the name of the server

0.000s

SMTP server type is hidden

Passed

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

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

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

Web

Website

Url
https://67.231.158.194/
Https
Title
Unknown
Description
Unknown
First paragraph
Unknown
Url
http://67.231.158.194/
Reachable
No
Url
https://67.231.158.194/
Title
Unknown
Description
Unknown
Response time
0.389 second
Server
Unknown
Powered by
Unknown
Encoding
iso-8859-1
HSTS

Headers

  • Connection: close
  • Content-Length: 10
  • Content-Type: text/html; charset=iso-8859-1
  • Date: Mon, 25 Oct 2021 09:45:12 GMT
  • Server:
  • Strict-Transport-Security: max-age=31536000; includeSubDomains

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

HTTP port (80) is open

The http port is close while there is a website.

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

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

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 server version is hidden

Passed

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

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

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