Contact us by email
|
For media enquiries please contact: Alex Bishop at Racepoint Group
|
Please choose the email address for your specific enquiry.
General Contact
|
Mail address to use:
|
Issues regarding:
|
| ncc@ripe.net | General contact address. |
| abuse@ripe.net | Network Abuse (Spamming or Hacking) Issues. |
| new-lir@ripe.net | Local Internet Registries interested in becoming members. |
| legacy@ripe.net | Legacy space (members and non-members) |
Members
|
Mail address to use:
|
Issues regarding:
|
| hostmaster@ripe.net | IP address and AS Number requests from Local Internet Registries. |
| lir-help@ripe.net | Questions related to Registration Services. |
| contact@ripe.net | Questions, feedback and input. |
| training@ripe.net | Registration for and questions about Training Courses. |
| billing@ripe.net | All questions related to billing issues from Local Internet Registries. |
| agm@ripe.net | RIPE NCC General Meetings and RIPE NCC Executive Board elections. |
RIPE Database
|
Mail address to use:
|
Issues regarding:
|
| auto-dbm@ripe.net | Automatic updates of the RIPE Database. |
| ripe-dbm@ripe.net | Questions related to the RIPE Database and the delegation of Reverse DNS Zones. |
| test-dbm@ripe.net | Automatic updates of the TEST Database. |
| auto-rrcc@ripe.net | To receive automatic reports from the Routing Registry Consistency Check project. |
Measurement & Analysis Services
|
Mail address to use:
|
Issues regarding:
|
| ttm@ripe.net | All issues related to Test Traffic Measurements. |
| ris@ripe.net | Questions related to the Routing Information Service project. |
| http://www.ris.ripe.net/peerreg.cgi | Peering with the Routing Information Service project (AS12654). |
| dnsmon@ripe.net | All issues relating to the DNSMON service |
| stat@ripe.net | All issues relating to the prototype RIPEstat service |
DNS Services
|
Mail address to use:
|
Issues regarding:
|
| k-peerings@ripe.net | Requests for K-root peerings (AS 25152). |
| kroot-ops@ripe.net | Non-peering queries about K-root operations. |
| k-anycast@ripe.net | General questions and comments about the K-root anycast infrastructure. |
| dns-help@ripe.net | Questions about any of the other DNS services provided by the RIPE NCC (AS 112, ccTLD secondary service, ENUM, etc). |
Network Operations
|
Mail address to use:
|
Issues regarding:
|
| ops@ripe.net | RIPE NCC daily operations (system administration/maintenance). |
| hostcount-workers@ripe.net | Persons performing hostcounts for their domain. |
| peerings@ripe.net | Contact point for inter AS peerings at the RIPE NCC in AS3333. |
Greylisting
The RIPE NCC uses greylisting on its mail servers in order to reduce the amount of spam recieved.
Greylisting works by sending a temporary SMTP error the first time an email is received from an unknown sender. Any legitimate mail servers that receive this error will resend the email successfully. The bulk mailers used by spammers do not usually try to resend email that is returned and so the spam is blocked on the first and only attempt at delivery.
Legitimate emails to the RIPE NCC should not be affected by greylisting. However, if you have any problem sending email, please contact ops@ripe.net.
