Skip to content
thenetworkery

Network report

Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.

IP address, prefix or AS number

AS208353 ·

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS208353"
JSON Docs

Warning: AS208353 (LFDJ2-AS) announces 6 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS208353
HolderLFDJ2-AS La Francaise des Jeux
AllocationRIPE NCC, France (FR), allocated 2019-08-21
Prefixes (IPv4 / IPv6)6 / 0
RPKI valid0% (0 / 6)
Upstreams and peers2

What to fix

  1. Warning

    No IPv6 prefixes announced.

    Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

    Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

    Open in ASN & BGP prefix lookup

  2. Warning

    6 of 6 announced prefixes have no ROA (RPKI not found): 194.4.214.0/24, 194.4.216.0/24, 194.4.217.0/24, 194.4.218.0/24, 194.4.219.0/24 (+1).

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS208353 and a max length equal to the prefix length:

    194.4.214.0/24 AS208353 max-length /24
    194.4.216.0/24 AS208353 max-length /24
    194.4.217.0/24 AS208353 max-length /24
    194.4.218.0/24 AS208353 max-length /24
    194.4.219.0/24 AS208353 max-length /24
    194.4.220.0/24 AS208353 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    2 of 6 announced prefixes have no IRR route object: 194.4.214.0/24, 194.4.220.0/24.

    Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.

    Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS208353 in your RIR’s IRR database (or RADB).

    route: 194.4.214.0/24
    origin: AS208353
    
    route: 194.4.220.0/24
    origin: AS208353

    Open in ASN & BGP prefix lookup

  4. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS208353 announces 6 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 6 of 6 announced prefixes have no ROA (RPKI not found): 194.4.214.0/24, 194.4.216.0/24, 194.4.217.0/24, 194.4.218.0/24, 194.4.219.0/24 (+1).
  • Warning: 2 of 6 announced prefixes have no IRR route object: 194.4.214.0/24, 194.4.220.0/24.
  • Info: 2 upstreams and peers, 1 downstream networks seen.
HolderLFDJ2-AS La Francaise des Jeux
IPv4 prefixes6
IPv6 prefixes0
RPKI6 not found
Without IRR route object2
Downstream networks1
Routes to fix
PrefixRPKI
194.4.214.0/24 No ROA
194.4.216.0/24 No ROA
194.4.217.0/24 No ROA
194.4.218.0/24 No ROA
194.4.219.0/24 No ROA
194.4.220.0/24 No ROA

Upstreams and peers seen to the left 2

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameLFDJ2-AS
HandleAS208353
RangeAS208353
Statusactive
Registered2019-08-21T07:20:30Z
Last changed2019-08-21T07:20:30Z
Abuse contactjbosler@lfdj.com
Allocation
Registry (RIR)RIPE NCC
CountryFrance (FR)
Delegated on2019-08-21
StatusAllocated
Delegated rangeAS208353

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
registrant LIR-FR-JEUX-MNT
registrant La Francaise des Jeux
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role jbosler@lfdj.com

Source: https://rdap.db.ripe.net/autnum/208353. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.

Open in WHOIS / RDAP lookup
PeeringDB PeeringDB did not answer: HTTP 404
  • Warning: PeeringDB did not answer: HTTP 404

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup