Your IP address is 3.236.80.119
Please select your question category
Search FAQs
View all frequently asked questions
View FAQ Tags

AFRINIC membership and resources related billing FAQs.

AFRINIC WHOIS related FAQs

General FAQs related to AFRINIC activites

MyAFRINIC portal related FAQs

Membership related queries

FAQ for Existing members

AFRINIC BPKI Services

FAQs related to IPv4 Exhaustion and its impact on AFRINIC

FAQs - All FAQs

AFRINIC can accept part payment in settlement of fee invoices. However, such form of payment must have prior approval of AFRINIC Executive management before being effected. Request for part payment must be made in writing and AFRINIC shall consider these requests on a case by case basis.

 

YES. Any changes in members billing category shall be communicated to the members immediately such changes occur. Such communication shall be by email addressed to existing registered contacts in AFRINIC database.

All fee are quoted in US DOLLARS and invoices are issued in US Dollars

NO. In the case of a New member, funds must be in AFRINIC bank account and an original Registration Service Agreement must have been received by the Member Services prior to the release of requested resources.

An Applicant becomes a member after all the New Member Registration criteria have been validated by the Hostmaster team, the initial Setup fee and membership fee have been credited to AFRINIC bank account, an original Registration Service Agreement has been received 

 

AFRINIC accepts major international Credit Cards like VISA, MASTER CARD and any other cards as approved by AFRINIC bank. If in doubt, please contact billing@afrinic.net for assistance. 

At the moment, AFRINIC does not issue formal individual receipt for fees received. An email acknowledgement is sent to members. However, one will be provided should the member so require. Please contact billing@afrinic.net for assistance.

 

NO, AFRINIC only maintains a US Dollar account where fees from members are to be transferred into. This minimizes AFRINIC exposure to currency fluctuations.

A BPKI Certificate (also known as a client X.509 certificate) is a Digital certificate provided to identify the holder of such certificate while performing online transaction. In case of AFRINIC, the client certificate delivered will hold your NIC-HANDLE as Common Name (CN). AFRINIC BPKI certificate will be used to digitally certify Organisation members right to perform and access certain services online such as RPKI and Board Election.

Tags: bpki, election

The Digital Certificate issued by AFRINIC allows us to confirm that you are indeed the representative of a member organisation exercising your right to vote.

Tags: vote

The enrolment of your certificate is a process by which your Digital Certificate is integrated into your browser to be automatically used for authentication purpose. The process of this integration is not the same for all browsers. The process pre-defined in the engine we use at AFRINIC is only compatible with Firefox. We are working to extend this to as many browsers as possible. 

Tags: certificate

Any Administrative contact or any registered contact that has been assigned the ‘Voter’ role can cast a vote. 

You must be an authorised contact of your organisation to obtain a BPKI certificate. If you are an Administrative contact of a Member Organisation you should sent a mail to bpki-help@afrinic.net with proofs of your identity. If you are a technical, billing, abuse or general contact, you will be asked to request a BPKI certificate that has to be approved by the Administrative contact of your Organisation. Click here for more Information.

 

If you do not see the link to the vote, this means that you have already been issued with a Proxy for the vote. In such case, you cannot exercise your right of vote online anymore. You need to sign the Proxy document and give it to your representative for an onsite vote.

This is because you have not been assigned the ‘Voter’ role. Only administrative contacts of the organisation can appoint the ‘Voter’ role.

Profile Information

Application afterLoad: 0.003 seconds, 0.72 MB
Application afterInitialise: 0.053 seconds, 2.70 MB
Application afterRoute: 0.093 seconds, 5.96 MB
Application afterDispatch: 0.165 seconds, 9.22 MB
Application afterRender: 0.352 seconds, 11.77 MB

Memory Usage

12444464

33 queries logged

  1. SELECT m.*, c.`option` AS component
      FROM www3menu AS m
      LEFT JOIN www3components AS c
      ON m.componentid = c.id
      WHERE m.published = 1
      ORDER BY m.sublevel, m.parent, m.ordering
  2. SELECT jf_content.reference_field, jf_content.VALUE, jf_content.reference_id, jf_content.original_value

      FROM www3jf_content AS jf_content

      WHERE jf_content.language_id=1
           
      AND jf_content.published=1
       
      AND jf_content.reference_id IN(1,11,20,304,324,262,231,275,340,393,791,661,12,51,348,805,831,13,52,154,795,14,24,53,793,15,797,16,62,803,17,799,68,97,27,387,619,191,221,172,170,76,171,337,418,521,845,175,174,177,237,176,499,511,455,481,523,547,671,184,185,188,423,837,527,179,181,204,235,156,158,159,384,475,675,629,160,161,162,157,192,621,268,270,266,321,264,265,338,416,483,519,843,276,283,278,282,477,677,279,631,280,281,429,277,382,305,306,307,308,424,835,317,330,318,319,320,325,326,327,328,529,341,342,343,345,350,349,408,351,354,745,489,509,356,479,525,549,673,388,400,403,404,405,406,419,513,399,394,396,397,395,617,615,663,665,801,414,163,731,733,735,737,715,739,741,789,743,269,271,272,292,289,290,291,293,294,339,295,420,386,807,811,285,286,288,819,383,287,515,567,809,817,415,284,633,763,315,312,561,563,565,767,314,380,517,332,333,334,335,336,370,346,347,311,378,787,352,364,362,365,833,719,366,367,368,411,412,453,825,379,357,358,359,360,361,371,431,459,463,467,469,471,473,531,533,537,539,541,543,545,599,609,601,605,485,487,491,493,495,497,551,553,557,559,841,573,575,577,579,581,583,585,591,589,777,779,813,749,751,753,755,747,757,759,761,783,373,374,375,376,721,417,829,669,353,413,461,535,781,727,667,611,597,603,815,769,635,637,639,641,645,643,647,649,651,653,655,657,659,785,821,823,827,697,701,703,705,707,709,711)
       
      AND jf_content.reference_table='menu'
  3. SELECT *
      FROM www3rokcandy
      WHERE published=1
  4. SELECT template
      FROM www3templates_menu
      WHERE client_id = 0
      AND (menuid = 0 OR menuid = 400)
      ORDER BY menuid DESC
      LIMIT 0, 1
  5. SELECT *
      FROM www3fsf_settings
  6. SELECT *
      FROM www3fsf_settings_big
  7. SELECT *
      FROM www3fsf_settings_view
  8. SELECT *
      FROM www3fsf_faq_cat
      WHERE published = 1
      ORDER BY ordering
  9. SELECT *
      FROM www3fsf_user
      WHERE user_id = '0'
  10. SELECT id, link
      FROM www3menu
      WHERE link LIKE '%option=com_fsf%'
      AND published = 1
  11. SELECT jf_content.reference_field, jf_content.VALUE, jf_content.reference_id, jf_content.original_value

      FROM www3jf_content AS jf_content

      WHERE jf_content.language_id=1
           
      AND jf_content.published=1
       
      AND jf_content.reference_id IN(400,388,404,393,394,395,396,397,399,403,405,406,419,513)
       
      AND jf_content.reference_table='menu'
  12. SELECT *
      FROM www3fsf_faq_faq
      WHERE published = 1
      ORDER BY ordering
  13. SELECT *
      FROM www3fsf_faq_faq
      WHERE published = 1
      ORDER BY ordering
      LIMIT 120, 15
  14. SELECT *
      FROM www3fsf_faq_tags
      WHERE faq_id IN (121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135)
      GROUP BY tag
      ORDER BY tag
  15. SELECT COUNT(*) AS cnt
      FROM www3fsf_faq_tags
  16. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  17. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  18. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  19. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  20. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  21. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  22. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  23. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  24. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  25. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  26. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  27. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  28. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  29. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  30. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  31. SELECT *
      FROM www3fsf_glossary
      WHERE  published = 1  
      ORDER BY LENGTH(word) DESC
  32. SELECT id, title, module, POSITION, content, showtitle, control, params
      FROM www3modules AS m
      LEFT JOIN www3modules_menu AS mm
      ON mm.moduleid = m.id
      WHERE m.published = 1
      AND m.access <= 0
      AND m.client_id = 0
      AND ( mm.menuid = 400 OR mm.menuid = 0 )
      ORDER BY POSITION, ordering
  33. SELECT jf_content.reference_field, jf_content.VALUE, jf_content.reference_id, jf_content.original_value

      FROM www3jf_content AS jf_content

      WHERE jf_content.language_id=1
           
      AND jf_content.published=1
       
      AND jf_content.reference_id IN(79,330,35,326,331,347,345,329,319,292,335)
       
      AND jf_content.reference_table='modules'

Language Files Loaded

Untranslated Strings Diagnostic

None

Untranslated Strings Designer

None