Jump to content

212.117.161.81 false positives ?


Recommended Posts

Many times your soft stop the ip adress : 212.117.161.81

Or this is the address of the society root eSolutions in Luxembourg.

I find with a whois this informations. Is a false alert ?

Regards

% This is the RIPE Database query service.

% The objects are in RPSL format.

%

% The RIPE Database is subject to Terms and Conditions.

% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Note: This output has been filtered.

% To receive output for a database update, use the "-B" flag.

% Information related to '212.117.160.0 - 212.117.175.255'

inetnum: 212.117.160.0 - 212.117.175.255

netname: SERVER-LU

descr: root eSolutions

country: LU

admin-c: AB99-RIPE

tech-c: RE655-RIPE

status: ASSIGNED PA

mnt-by: ROOT-MNT

source: RIPE # Filtered

role: root eSolutions

address: 35, rue John F. Kennedy

address: 7327 Steinsel

address: Luxembourg

phone: +352 20.500

fax-no: +352 20.500.500

e-mail: info@root.lu

remarks:

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

remarks: | Operational Issues: |

remarks: | noc@as5577.net |

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

remarks: | Abuse and Spam: |

remarks: | abuse@as5577.net |

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

remarks:

admin-c: RE655-RIPE

tech-c: AB99-RIPE

nic-hdl: RE655-RIPE

mnt-by: ROOT-MNT

source: RIPE # Filtered

person: Andy BIERLAIR

address: root eSolutions

address: 35, rue John F. Kennedy

address: 7327 Steinsel

address: Luxembourg

phone: +352 20.500

fax-no: +352 20.500.500

nic-hdl: AB99-RIPE

mnt-by: ROOT-MNT

remarks:

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

remarks: | I did *NOT* spam your mailbox! |

remarks: | I will *NOT* reply to abuse mails! |

remarks: | Please contact abuse@as5577.net ! |

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

remarks:

e-mail: ab@root.lu

source: RIPE # Filtered

% Information related to '212.117.160.0/19AS5577'

route: 212.117.160.0/19

descr: root eSolutions

origin: AS5577

mnt-by: ROOT-MNT

source: RIPE # Filtered

Link to post
Share on other sites

It could be that it's simply not detected, or it could've been incoming rather than outgoing. The only way to verify that is using a packet filter such as TCPView, Wireshark or even in some cases, your firewalls logs.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.