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

AS38627 · 

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

Warning: AS38627 (BAIDUJP) announces nothing right now. 3 warnings

AS pageAS38627
HolderBAIDUJP - Baidu, Inc.
AllocationAPNIC, Japan (JP), allocated 2007-08-20
Prefixes (IPv4 / IPv6)0 / 0
Peering policyOpen

What to fix

  1. Warning

    No abuse contact is published for AS38627.

    Other networks send reports of spam, attacks and hacked machines to the abuse contact. Without one, reports go nowhere and blocklists may list the whole range.

    Fix: Add an abuse contact to the registration: abuse-c in the RIPE database, an Abuse POC at ARIN, an abuse mailbox (IRT) at APNIC, AFRINIC or LACNIC.

    Open in WHOIS / RDAP lookup

  2. Warning

    No IRR as-set is listed.

    Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.

    Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.

    Open in PeeringDB lookup

  3. 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.

    Open in PeeringDB lookup

Checks

Routing and RPKI AS38627 is not announcing anything right now.
  • Info: AS38627 is not announcing anything right now.
HolderBAIDUJP - Baidu, Inc.
IPv4 prefixes0
IPv6 prefixes0
Downstream networks0

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

Open in ASN & BGP prefix lookup
Registration No abuse contact is published for AS38627.
  • Pass: Found at rdap.apnic.net.
  • Warning: No abuse contact is published for AS38627.
NameBAIDUJP
HandleAS38627
RangeAS38627
CountryJP
Statusactive
Last changed2007-12-21T22:41:16Z
Allocation
Registry (RIR)APNIC
CountryJapan (JP)
Delegated on2007-08-20
StatusAllocated
Delegated rangeAS38627 – AS38656

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

Contacts
RoleNameEmail
technical, administrative RS2845JP
technical, administrative Japan Network Information Center hostmaster@nic.ad.jp

Source: https://rdap.apnic.net/autnum/38627. Registration data from rdap.apnic.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup
PeeringDB No IRR as-set is listed.
  • Pass: AS38627 is in PeeringDB as Baidu Japan.
  • Info: Peering policy: Open.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-07-27.
NetworkBaidu Japan (Baidu Japan)
AS numberAS38627
TypeContent, Asia Pacific
Websitehttps://www.baidu.jp
Prefixes (IPv4 / IPv6)0 / 0
TrafficNot Disclosed
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup