LIR Services FAQ

You can find up-to-date information and complete instructions in the DGTL.TECH Knowledgebase.

Sources of IP Geolocation Data

Initially, information about the IPs is kept in RIRs (Regional Internet Registry) whois databases such as the RIPE Whois Database and maintained by the organisation that owns the IP addresses, such as the ISPs.

COUNTRY attribute on the INETNUM and INET(6)NUM objects in the RIPE Whois Database:

Object in RIPE Database
inetnum:185.234.247.0 - 185.234.247.255
netname:UK-DGTL-20210121
country:NL
org:ORG-DTUL2-RIPE
admin-c:DGTL6-RIPE
tech-c:DGTL6-RIPE
status:ALLOCATED PA
mnt-by:MNT-DGTL
mnt-by:RIPE-NCC-HM-MNT
mnt-lower:MNT-DGTL
mnt-routes:MNT-DGTL
created:2021-01-21T13:37:33Z
last-modified:2021-01-21T13:44:34Z
source:RIPE

There is no provision to define a more accurate location such as a city, knowing that the end user's location generally differs from the registered administrative contact location of an ISP, making the geolocation data's accuracy low.

The RIPE Database offers the geoloc: attribute on ORGANISATION and INET(6)NUM objects that may or may not be used as an additional source of information by these providers.

A number of companies provide geolocation services, including:

Updating IP Geolocation Databases

We cannot guarantee desired geolocation for objects.

You should contact all providers above to ensure that your IP geolocation data is correct across the board. That makes perfect sense knowing that it is hard to tell which website uses which of these databases.

Most of your IP geolocation efforts should be centered around the IP geolocation databases as these databases are de facto the standard today.

An up-to-date entry in all the IP geolocation databases does not guarantee that your IP Address Space will be recognised appropriately everywhere. This happens because some content providers download the updates from the IP geolocation databases less frequently than others. If this happens to you, we advise contacting the specific content provider and asking them to download the IP geolocation updates.

Geofeeds

For the clients, we can add their resources to our Geofeed, which we public in RIPE Database.

Self-published IP Geolocation Data or simply a Geofeed, is an advanced topic. The first thing to mention is that the Geofeed is currently a draft and not an approved RFC. This fact, however, did not stop the internet community from embracing the concept. The first version of the draft was published in 2013, so it has been around for a while.

The Geofeed allows network operators to publish the IP geolocation for the IP blocks that are under their control. The feeds are published in the CSV format and contain the following information: ip_range,country,region,city,postal_code.

The idea is that the content providers will be able to process changes to your IP space geolocation automatically, based on the Geofeed that you publish, which saves you time on having to contact these providers individually to notify of any changes.

Unfortunately, currently, no standardised mechanism for advertising your feed to the rest of the world exists.

The Geofeeds are much easier to administer than the geoloc entries. The Geofeeds are just a flat file that can be edited at speed. At the same time, geoloc entries are troublesome to manage at scale (i.e., when you subdivide IP blocks that are then in use at different locations) as they require separate objects in the whois databases.

↑ Back to top

How to remove your IP found in Real-Time Blacklist (RBL)

Getting your IP off an RBL takes a few steps. Here's how you can do it.

  1. Identify the Blacklist
    Use tools like RBL TOOL, MXToolbox, Spamhaus, or BlacklistAlert.org to check which RBL has flagged your IP. Each tool will show:
    • The name of the blacklist.
    • The reason for the listing (if provided).
    • A link to the blacklist's website.
  2. Investigate the Cause
    Before requesting removal, figure out why your IP was flagged:
    • Check email logs for spam-like behavior or large volumes of emails sent in a short time.
    • Look for server issues like unauthorized access or misconfigurations.
    • Scan your network for malware or botnets that may be sending spam without your knowledge.
    Fix any problems you find to avoid being re-listed.
  3. Resolve the Issue
    Take these steps to improve your email practices:
    • Secure Your Emails: Set up SPF, DKIM, and DMARC to prevent unauthorized use of your domain.
    • Clean Your Email List: Remove inactive or fake email addresses. Always verify opt-ins.
    • Protect Your Network: Use antivirus software to remove malware or botnets.
  4. Request Delisting
    Go to the website of the blacklist where your IP is listed. Each website may ask for details like:
    • Evidence of resolving the issue.
    • An explanation of what went wrong.
  5. Monitor and Stay Safe
    Once your IP is removed:
    • Regularly check your IP to ensure it stays clear of blacklists.
    • Follow email best practices: avoid sending spam-like emails; use authentication protocols like SPF and DKIM; send emails gradually to avoid sudden volume spikes.

Popular RBLs & Guidelines

Spamhaus

One of the most trusted RBLs, Spamhaus lists IPs involved in sending spam, hosting malware, or violating email policies.

Why They Block:

  • Sending spam emails
  • Hosting phishing/malware websites
  • Sending from dynamic IPs

Return Codes: 127.0.0.2 Spam activity, 127.0.0.10 Breaking email rules

Delisting: Visit Spamhaus Removal Center; follow steps, fix problems, request removal.

Barracuda

Barracuda blocks IPs reported for spam or caught in spam traps.

Why They Block:

  • Email reports as spam
  • Sending to spam traps (fake emails catching spammers)
  • Links to harmful websites

Return Code: 127.0.0.2 Spam activity detected

Delisting: Use Barracuda Lookup Tool; fix issue; submit removal form.

SpamCop

SpamCop uses user reports to find IPs sending spam.

Why They Block:

  • User spam reports
  • Spam-like email appearance

Return Code: 127.0.0.2 Spam complaints detected

Delisting: Use SpamCop Lookup Tool; fix issue; submit removal request.

Prevent RBL Blacklisting

  1. Set up SPF, DKIM, DMARC
  2. Warm up email domain gradually (avoid sudden volume)
  3. Monitor sender reputation; watch bounce rates/complaints
  4. Clean email lists regularly; remove unverified contacts
  5. Avoid spam traps; use double opt-ins
  6. Send personalized emails (not bulk/generic)
  7. Use reliable email infrastructure
  8. Don't make evil, and be cool.
↑ Back to top

How to Get Your Own ASN

What is an ASN and why do I need one?

An ASN (Autonomous System Number) is a unique identifier that allows your network to operate independently using the BGP (Border Gateway Protocol).

You need an ASN if you want to:

  • Announce IP prefixes under your control
  • Peer with multiple upstream providers
  • Implement custom routing policies

Essential for: ISPs, hosting providers, large enterprises, infrastructure-focused tech users.

Can DGTL.TECH help register an ASN with RIPE?

Yes. DGTL.TECH guides through the process and acts as sponsoring LIR (Local Internet Registry), required by RIPE.

What documents and information are required?

  • Two upstream providers (peering partners/uplinks) with written BGP session agreements
  • Valid passport or government-issued ID
  • Clear technical justification for ASN request
  • Filled RIPE ASN request form

What exactly are "uplinks" or "peering partners"?

Uplinks are existing ASNs (Autonomous Systems) that agree to route traffic to/from your ASN via BGP.

These can be:

  • Internet service providers
  • Hosting companies
  • Data centers
  • Internet exchanges (IXPs)

They must agree to peer with your ASN and confirm it to RIPE (usually via email confirmation).

Where can I find uplink providers?

  • Current hosting provider/data center
  • ISPs offering BGP multihoming
  • Peering platforms like IXPs (LINX, DE-CIX)
  • Forums: RIPE mailing lists, PeeringDB

How long does it take to get an ASN?

RIPE NCC review: 2–4 business days typically. Faster approval with clear, complete uplink confirmations.

Once I have the ASN, how do I use it?

  • Configure BGP on router/virtual router
  • Establish BGP sessions with two confirmed uplinks
  • Announce IP prefixes (PI space from RIPE or provider-assigned PA space)
  • Ensure redundancy and routing policy enforcement

You can use your ASN within RIPE service regions (Europe, Middle East, Central Asia). DGTL.TECH offers ASN sponsorship and full application support. If you're ready to begin or have further questions, contact us via live chat or our contact form.

↑ Back to top

Get in touch.

Need help with LIR services?

Contact Us