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.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
Warning: AS48144 (NETWORKTECH) announces 1 IPv4 and 2 IPv6 prefixes. 3 warnings
| AS page | AS48144 |
|---|---|
| Holder | NETWORKTECH Network Technology Harald Firing Karlsen |
| Allocation | RIPE NCC, Norway (NO), allocated 2008-10-17 |
| Prefixes (IPv4 / IPv6) | 1 / 2 |
| RPKI valid | 67% (2 / 3) |
| Upstreams and peers | 1 |
| Peering policy | Restrictive |
What to fix
-
Warning
1 of 3 announced prefixes have no ROA (RPKI not found): 2001:67c:1c00::/40.
Without a ROA, networks cannot tell your routes from a hijack.
Fix: Create a ROA for each at your RIR portal, with origin AS48144 and a max length equal to the prefix length:
2001:67c:1c00::/40 AS48144 max-length /40
-
Warning
1 of 3 announced prefixes have no IRR route object: 2001:67c:1cff::/48.
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 AS48144 in your RIR’s IRR database (or RADB).
route6: 2001:67c:1cff::/48 origin: AS48144
-
Warning
No public NOC, policy or technical contact.
Other networks use these addresses to set up peering and to reach you during an incident.
Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.
Checks
Routing and RPKI 1 of 3 announced prefixes have no ROA (RPKI not found): 2001:67c:1c00::/40.
- Pass: AS48144 announces 1 IPv4 and 2 IPv6 prefixes.
- Warning: 1 of 3 announced prefixes have no ROA (RPKI not found): 2001:67c:1c00::/40.
- Info: 2 of 3 announced prefixes are RPKI valid.
- Warning: 1 of 3 announced prefixes have no IRR route object: 2001:67c:1cff::/48.
- Info: One upstream or peer seen (AS50304): an outage there takes the whole network off the internet.
| Holder | NETWORKTECH Network Technology Harald Firing Karlsen |
|---|---|
| IPv4 prefixes | 1 |
| IPv6 prefixes | 2 |
| RPKI | 2 valid · 1 not found |
| Without IRR route object | 1 |
| Downstream networks | 0 |
| Prefix | RPKI |
|---|---|
| 2001:67c:1c00::/40 | No ROA |
Upstreams and peers seen to the left 1
Announced prefixes 3
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration Found at rdap.db.ripe.net.
- Pass: Found at rdap.db.ripe.net.
| Name | NETWORKTECH |
|---|---|
| Handle | AS48144 |
| Range | AS48144 |
| Status | active |
| Registered | 2008-10-17T11:16:30Z |
| Last changed | 2021-12-12T15:30:22Z |
| Abuse contact | abuse@orb.no |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | Norway (NO) |
| Delegated on | 2008-10-17 |
| Status | Allocated |
| Delegated range | AS48144 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | AS48144-MNT | |
| registrant | Network Technology Harald Firing Karlsen | |
| registrant | RIPE-NCC-END-MNT | |
| abuse | Abuse-C Role | abuse@orb.no |
Source: https://rdap.db.ripe.net/autnum/48144. 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 lookupPeeringDB No public NOC, policy or technical contact.
- Pass: AS48144 is in PeeringDB as Orb.
- Info: Peering policy: Restrictive.
- Info: No internet exchange ports are listed.
- Warning: No public NOC, policy or technical contact.
- Info: The record was last updated 2022-07-27.
| Network | Orb |
|---|---|
| AS number | AS48144 |
| Type | , Not Disclosed |
| Website | http://www.orb.no |
| IRR as-set | AS-ORB |
| Prefixes (IPv4 / IPv6) | 10 / 10 |
| Traffic | Balanced |
| Peering policy | Restrictive |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2022-07-27 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup