Analysis report on IP address: 209.183.50.151

209.183.50.151 has no website

Generated on
15 Nov 2021 02:32
Duration of the analysis
186.8s
Share

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

Congratulation

Your domain is really well configured

DNS

Dns servers for 50.183.209.in-addr.arpa

209.183.50.151 was detected as ipv4

Query informations

Server
f.root-servers.net
[ 192.5.5.241 ]
Duration
70 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

Server
alninetdns.mycingular.net
[ 209.183.50.151 ]
Duration
116 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
alpinetdns.mycingular.net
[ 209.183.35.23 ]
Duration
99 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
bthinetdns.mycingular.net
[ 209.183.54.151 ]
Duration
155 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
schinetdns.mycingular.net
[ 209.183.33.23 ]
Duration
103 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0
DNSSEC analysis not possible on an IP

Ip

Informations

Ip
209.183.50.151
Type
ipv4
Reverse
alninetdns.mycingular.net
ARPA
151.50.183.209.in-addr.arpa
Class C
209.183.50.0/24
ASN
20057 ATT-MOBILITY-LLC-AS20057
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:       209.183.32.0 - 209.183.63.255
CIDR:           209.183.32.0/19
NetName:        ATT-MOBILITY-LLC-209-183-32-0
NetHandle:      NET-209-183-32-0-1
Parent:         NET209 (NET-209-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   AT&T Mobility LLC (ATTMO-3)
RegDate:        2001-04-10
Updated:        2012-03-20
Ref:            https://rdap.arin.net/registry/ip/209.183.32.0



OrgName:        AT&T Mobility LLC
OrgId:          ATTMO-3
Address:        7277 164th Ave NE
Address:        ATTN:  IP Management
City:           Redmond
StateProv:      WA
PostalCode:     98052
Country:        US
RegDate:        2008-10-10
Updated:        2021-06-26
Comment:        For policy abuse issues contact:     dXaJh3k= [at] att.net
Comment:        
Comment:        Send all subpoena, Internet, Court order related matters to:
Comment:        
Comment:        ATT National Compliance Center
Comment:        11760 US Hwy 1, Suite 600
Comment:        North Palm Beach, FL  33408
Comment:        Phone Number: 1-800-635-6840
Comment:        Fax Number:  1-888-938-4715
Comment:        Email:  d4OBhHd5gog= [at] att.com
Ref:            https://rdap.arin.net/registry/entity/ATTMO-3


OrgAbuseHandle: ATTAB1-ARIN
OrgAbuseName:   ATT Abuse
OrgAbusePhone:  +1-919-319-8130 
OrgAbuseEmail:  dXaJh3k= [at] att.net
OrgAbuseRef:    https://rdap.arin.net/registry/entity/ATTAB1-ARIN

OrgTechHandle: IPADM2-ARIN
OrgTechName:   IPAdmin ATT Internet Services
OrgTechPhone:  +1-888-510-5545 
OrgTechEmail:  fYR1eIF9gg== [at] att.com
OrgTechRef:    https://rdap.arin.net/registry/entity/IPADM2-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.003s

Mail

There is no mail server. Please test alninetdns.mycingular.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

There is no web server. Please test alninetdns.mycingular.net.

Url
http://209.183.50.151/
Timeout
Yes
Url
https://209.183.50.151/
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