Analysis report on IP address: 203.190.128.135
Congratulation
Your domain is really well configured
DNS
Dns servers for 128.190.203.in-addr.arpa
203.190.128.135 was detected as ipv4
- Name
- pri.stpi.in
- IPs
Possible problem in Dns Tree
We have detected the followings errors on one or more server(s).
Consult Tree for more details.
- Server failure or format error
- Refuse to respond or is in timeout state.
Query informations
- Server
- d.root-servers.net
[ 199.7.91.13 ] - Duration
- 9 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- a.in-addr-servers.arpa
- IPs
- Name
- b.in-addr-servers.arpa
- IPs
- Name
- c.in-addr-servers.arpa
- IPs
- Name
- d.in-addr-servers.arpa
- IPs
- Name
- e.in-addr-servers.arpa
- IPs
- Name
- f.in-addr-servers.arpa
- IPs
Query informations
- Server
- a.in-addr-servers.arpa
[ 199.180.182.53 ] - Duration
- 150 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- apnic.authdns.ripe.net
- IPs
- Name
- apnic1.dnsnode.net
- IPs
- Name
- ns2.apnic.net
- IPs
- Name
- ns3.lacnic.net
- IPs
- Name
- rirns.arin.net
- IPs
Query informations
- Server
- b.in-addr-servers.arpa
[ 199.253.183.183 ] - Duration
- 36 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- apnic.authdns.ripe.net
- IPs
- Name
- apnic1.dnsnode.net
- IPs
- Name
- ns2.apnic.net
- IPs
- Name
- ns3.lacnic.net
- IPs
- Name
- rirns.arin.net
- IPs
Query informations
- Server
- c.in-addr-servers.arpa
[ 196.216.169.10 ] - Duration
- 184 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- apnic.authdns.ripe.net
- IPs
- Name
- apnic1.dnsnode.net
- IPs
- Name
- ns2.apnic.net
- IPs
- Name
- ns3.lacnic.net
- IPs
- Name
- rirns.arin.net
- IPs
Query informations
- Server
- d.in-addr-servers.arpa
[ 200.10.60.53 ] - Duration
- 250 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- apnic.authdns.ripe.net
- IPs
- Name
- apnic1.dnsnode.net
- IPs
- Name
- ns2.apnic.net
- IPs
- Name
- ns3.lacnic.net
- IPs
- Name
- rirns.arin.net
- IPs
Query informations
- Server
- e.in-addr-servers.arpa
[ 203.119.86.101 ] - Duration
- 264 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- apnic.authdns.ripe.net
- IPs
- Name
- apnic1.dnsnode.net
- IPs
- Name
- ns2.apnic.net
- IPs
- Name
- ns3.lacnic.net
- IPs
- Name
- rirns.arin.net
- IPs
Query informations
- Server
- f.in-addr-servers.arpa
[ 193.0.9.1 ] - Duration
- 23 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- apnic.authdns.ripe.net
- IPs
- Name
- apnic1.dnsnode.net
- IPs
- Name
- ns2.apnic.net
- IPs
- Name
- ns3.lacnic.net
- IPs
- Name
- rirns.arin.net
- IPs
Query informations
- Server
- apnic.authdns.ripe.net
[ 193.0.9.9 ] - Duration
- 193 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- pri.stpi.in
- IPs
- Name
- stpb.soft.net
- IPs
Query informations
- Server
- apnic1.dnsnode.net
[ 194.146.106.106 ] - Duration
- 17 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- pri.stpi.in
- IPs
- Name
- stpb.soft.net
- IPs
Query informations
- Server
- ns2.apnic.net
[ 203.119.95.53 ] - Duration
- 19 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- pri.stpi.in
- IPs
- Name
- stpb.soft.net
- IPs
Query informations
- Server
- ns3.lacnic.net
[ 200.3.13.14 ] - Duration
- 196 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- pri.stpi.in
- IPs
- Name
- stpb.soft.net
- IPs
Query informations
- Server
- rirns.arin.net
[ 199.253.249.53 ] - Duration
- 140 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- pri.stpi.in
- IPs
- Name
- stpb.soft.net
- IPs
Query informations
- Server
- pri.stpi.in
[ 203.190.128.141 ] - Duration
- 135 ms
- Type
- unknown
- Headers
- RCODE : 0 AA : 1 TC : 0
Query informations
- Server
- stpb.soft.net
[ 164.164.4.5 ] - Duration
- 147 ms
- Type
- server_failure
- Headers
- RCODE : 5 AA : 0 TC : 0
The name server was unable to process this dns query due to a problem with the name server
Server refused to answer when edns query is performed.
Ip
Informations
- Ip
- 203.190.128.135
- Type
- ipv4
- Reverse
- dnsnoida.stpi.in
- ARPA
- 135.128.190.203.in-addr.arpa
- Class C
- 203.190.128.0/24
- ASN
- 9430 Software Technology Parks of India,Block-IV
- Organisation
- SN200-AP
- Maintainer
- MAINT-IN-IRINN
Reputation
- Blacklists
- Whois server
- whois.apnic.net
% [whois.apnic.net] % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html % Information related to '203.190.128.0 - 203.190.159.255' % Abuse contact for '203.190.128.0 - 203.190.159.255' is O3WCiH1BdXaJh3k= [at] noida.stpi.in' inetnum: 203.190.128.0 - 203.190.159.255 netname: STPI-NOIDA descr: Software Technology Parks of India descr: Class 'A' Internet Service Provider country: IN admin-c: SN200-AP tech-c: SN200-AP mnt-by: MAINT-IN-IRINN mnt-lower: MAINT-IN-STPIN mnt-routes: MAINT-IN-STPIN mnt-irt: IRT-STPI-IN status: ALLOCATED PORTABLE last-modified: 2013-02-06T23:35:10Z source: APNIC % Information related to '203.190.128.0/24AS9430' route: 203.190.128.0/24 descr: Software Technology Parks of India,Block-IV descr: Ganga Software Technology Complex descr: Sector-29, Noida,Uttar Pradesh.PIN - 201303 country: IN origin: AS9430 mnt-by: MAINT-IN-STPIN last-modified: 2008-09-04T07:54:28Z source: APNIC % This query was served by the APNIC Whois Service version 1.88.15-SNAPSHOT (WHOIS-UK4)
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
There is no mail server. Please test dnsnoida.stpi.in.
- Name
- dnsnoida.stpi.in
- IP
- 203.190.128.135
- Accessible
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.
documentation0.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
EHLO command is accepted
Skipped
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
MX servers accept postmaster@ address
Skipped
According to the RFC 5321, SMTP server should accept postmaster@yourDomain as a recipient.
RFC0.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 dnsnoida.stpi.in.
- Url
- http://203.190.128.135/
- Timeout
- Yes
- Url
- https://203.190.128.135/
- 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)
RFC0.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.
documentation0.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).
documentation0.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