Analysis report on IP address: 67.212.240.34

67.212.240.34 has no website

Generated on
04 May 2021 17:48
Duration of the analysis
55.1s
Share

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

Resume

Cookies are secure

The HttpOnly flag was not found.

HTTP port (80) is open

The http port is close while there is a website.

HTTPS port (443) is open

The https port is close while there is a website.

DNS

Dns servers for 240.212.67.in-addr.arpa

67.212.240.34 was detected as ipv4

Query informations

Server
c.root-servers.net
[ 192.33.4.12 ]
Duration
29 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
35 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

Server
d.in-addr-servers.arpa
[ 200.10.60.53 ]
Duration
226 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
28 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

Server
ns5.twlakes.net
[ 63.135.176.42 ]
Duration
108 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns6.twlakes.net
[ 63.135.176.43 ]
Duration
108 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0
DNSSEC analysis not possible on an IP

Ip

Informations

Ip
67.212.240.34
Type
ipv4
Reverse
secure.twinlakes.net
ARPA
34.240.212.67.in-addr.arpa
Class C
67.212.240.0/24
ASN
19331 TWIN-LAKES
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.212.240.0 - 67.212.255.255
CIDR:           67.212.240.0/20
NetName:        TWIN-LAKES
NetHandle:      NET-67-212-240-0-1
Parent:         NET67 (NET-67-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       AS19331
Organization:   Twin Lakes Telephone Cooperative Corporation (TLTCC)
RegDate:        2008-11-11
Updated:        2018-11-08
Ref:            https://rdap.arin.net/registry/ip/67.212.240.0


OrgName:        Twin Lakes Telephone Cooperative Corporation
OrgId:          TLTCC
Address:        201 W. Gore Avenue
City:           Gainesboro
StateProv:      TN
PostalCode:     38562
Country:        US
RegDate:        2007-08-01
Updated:        2019-12-11
Ref:            https://rdap.arin.net/registry/entity/TLTCC


OrgDNSHandle: NOC242-ARIN
OrgDNSName:   Network Operations Center
OrgDNSPhone:  +1-931-268-2151 
OrgDNSEmail:  gnmIi4OGf32Cew== [at] twinlakes.net
OrgDNSRef:    https://rdap.arin.net/registry/entity/NOC242-ARIN

OrgNOCHandle: NOC242-ARIN
OrgNOCName:   Network Operations Center
OrgNOCPhone:  +1-931-268-2151 
OrgNOCEmail:  gnmIi4OGf32Cew== [at] twinlakes.net
OrgNOCRef:    https://rdap.arin.net/registry/entity/NOC242-ARIN

OrgRoutingHandle: NETWO7906-ARIN
OrgRoutingName:   Network Engineer
OrgRoutingPhone:  +1-931-268-2151 
OrgRoutingEmail:  foZ5dXt1gg== [at] twinlakes.net
OrgRoutingRef:    https://rdap.arin.net/registry/entity/NETWO7906-ARIN

OrgTechHandle: ADMIN3030-ARIN
OrgTechName:   ADMIN
OrgTechPhone:  +1-931-405-3231 
OrgTechEmail:  d4OEjYZ9e3yI [at] twinlakes.net
OrgTechRef:    https://rdap.arin.net/registry/entity/ADMIN3030-ARIN

OrgTechHandle: CSH147-ARIN
OrgTechName:   Heupel, Charles Shane
OrgTechPhone:  +1-931-268-2151 
OrgTechEmail:  dXaJh3k= [at] twlakes.coop
OrgTechRef:    https://rdap.arin.net/registry/entity/CSH147-ARIN

OrgAbuseHandle: ABUSE7741-ARIN
OrgAbuseName:   ABUSE
OrgAbusePhone:  +1-931-268-2151 
OrgAbuseEmail:  dXaJh3k= [at] twinlakes.net
OrgAbuseRef:    https://rdap.arin.net/registry/entity/ABUSE7741-ARIN

RAbuseHandle: CSH147-ARIN
RAbuseName:   Heupel, Charles Shane
RAbusePhone:  +1-931-268-2151 
RAbuseEmail:  dXaJh3k= [at] twlakes.coop
RAbuseRef:    https://rdap.arin.net/registry/entity/CSH147-ARIN

RNOCHandle: NOC242-ARIN
RNOCName:   Network Operations Center
RNOCPhone:  +1-931-268-2151 
RNOCEmail:  gnmIi4OGf32Cew== [at] twinlakes.net
RNOCRef:    https://rdap.arin.net/registry/entity/NOC242-ARIN

RTechHandle: ADMIN3030-ARIN
RTechName:   ADMIN
RTechPhone:  +1-931-405-3231 
RTechEmail:  d4OEjYZ9e3yI [at] twinlakes.net
RTechRef:    https://rdap.arin.net/registry/entity/ADMIN3030-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 secure.twinlakes.net.

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

Website

Url
https://67.212.240.34/
Https
Title
Unknown
Description
Unknown
First paragraph
Unknown
Url
http://67.212.240.34/
Timeout
Yes
Url
https://67.212.240.34/
Title
Unknown
Description
Unknown
Response time
0.665 second
Server
Unknown
Powered by
Unknown
Encoding
utf-8
HSTS

Headers

  • Cache-Control: no-store
  • Connection: Keep-Alive
  • Content-Security-Policy: default-src 'self' 'unsafe-inline' 'unsafe-eval' data: blob:; frame-ancestors 'self'
  • Content-Type: text/html; charset=utf-8
  • Date: Tue, 04 May 2021 17:49:05 GMT
  • Pragma: no-cache
  • Set-Cookie: webvpn=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/; secure, webvpn_as=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/; secure, webvpnc=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/; secure, webvpn_portal=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/; secure, webvpnSharePoint=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/; secure, samlPreauthSessionHash=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/; secure, acSamlv2Token=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/; secure, acSamlv2Error=; expires=Thu, 01 Jan 1970 22:00:00 GMT; path=/; secure, webvpnlogin=1; path=/; secure
  • Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Transfer-Encoding: chunked
  • X-Content-Type-Options: nosniff
  • X-Frame-Options: SAMEORIGIN
  • X-XSS-Protection: 1

Cookies are secure

The HttpOnly flag was not found.

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

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

HTTPS port (443) is open

The https 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 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

X-XSS-Protection header is present

Passed

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

Passed

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

Passed

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