Information related to '202.88.224.0 - 202.88.255.255' - abuse-mailbox: sysadmin[at]asianetindia.com

[A B]

Reports for '202.88.224.0 - 202.88.255.255' should go to sysadmin[at]asianetindia.com

inetnum:        202.88.224.0 - 202.88.255.255

netname: ASIANET

descr: Asianet is a ISP providing access through Cable.

country: IN

admin-c: DC1082-AP

tech-c: DC1082-AP

mnt-by: APNIC-HM

mnt-lower: MAINT-IN-ASIANET

mnt-routes: MAINT-IN-ASIANET

mnt-irt: IRT-ASIANET-IN

remarks: -+-+-+-+-+-+-+-+-+-

[...]

irt:            IRT-ASIANET-IN

address: 2 nd Floor , Leela Tower

address: Technopark,Kazhakuttam

address: Trivandrum

address: Kerala

e-mail: dineshchandran[at]asianet.co.in

abuse-mailbox: sysadmin[at]asianetindia.com

This is another case, where SpamCop fails to fetch the IRT object.

Lookup irt-asianet-in[at]whois.apnic.net

"whois irt-asianet-in[at]whois.apnic.net" (Getting contact from whois.apnic.net mirror)

Display data:

irt-asianet-in =

Note the missing address in the last line, also see the empty result on https://www.spamcop.net/sc?action=showwhois;cmd=irt-asianet-in, probably because this URI, linked from the "Display data" above is lacking the information, which whois server should be asked. So it looks like the whois irt-asianet-in[at]whois.apnic.net becomes just whois irt-asianet-in and therefore fails.