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

195.252.64.0/18 ·

curl -s "https://thenetworkery.com/api/v1/network-report?query=195.252.64.0%2F18"
JSON Docs

Warning: 195.252.64.0/18 is announced only as 18 more-specific routes. 1 warning

Announced as18 more-specific routes
HolderTELEKOM SRBIJA a.d.
AllocationRIPE NCC, Serbia (RS), allocated 1997-11-12
Size16,384 addresses
Abuse contactabuse@telekom.rs

What to fix

  1. Warning

    Reverse DNS is delegated for only 7 of the 10 zones checked.

    Addresses in the zones without a delegation have no PTR records.

    Fix: Create the missing reverse zones at your RIR.

    Open in DNS lookup

Checks

Routing and RPKI 195.252.120.0/21 from AS6700 is RPKI valid.
  • Info: 195.252.64.0/18 is not announced as a whole, only as 18 more-specific routes.
  • Pass: 195.252.120.0/21 from AS6700 is RPKI valid. 195.252.120.0/21
  • Pass: 195.252.92.0/22 from AS8400 is RPKI valid. 195.252.92.0/22
  • Pass: 195.252.108.0/22 from AS6700 is RPKI valid. 195.252.108.0/22
  • Pass: 195.252.112.0/22 from AS6700 is RPKI valid. 195.252.112.0/22
  • Pass: 195.252.70.0/23 from AS6700 is RPKI valid. 195.252.70.0/23
  • Pass: 195.252.80.0/23 from AS6700 is RPKI valid. 195.252.80.0/23
  • Pass: 195.252.98.0/23 from AS6700 is RPKI valid. 195.252.98.0/23
  • Pass: 195.252.106.0/23 from AS6700 is RPKI valid. 195.252.106.0/23
  • Pass: 195.252.118.0/23 from AS6700 is RPKI valid. 195.252.118.0/23
  • Pass: 195.252.64.0/24 from AS6700 is RPKI valid. 195.252.64.0/24
First seen2023-02-23
More-specific routes 18
More-specific routeOrigin ASRPKI
195.252.120.0/21 AS6700 RPKI valid
195.252.92.0/22 AS8400 RPKI valid
195.252.108.0/22 AS6700 RPKI valid
195.252.112.0/22 AS6700 RPKI valid
195.252.70.0/23 AS6700 RPKI valid
195.252.80.0/23 AS6700 RPKI valid
195.252.98.0/23 AS6700 RPKI valid
195.252.106.0/23 AS6700 RPKI valid
195.252.118.0/23 AS6700 RPKI valid
195.252.64.0/24 AS6700 RPKI valid
195.252.68.0/24 AS6700
195.252.82.0/24 AS8400
195.252.83.0/24 AS6700
195.252.88.0/24 AS8400
195.252.96.0/24 AS6700
195.252.101.0/24 AS6700
195.252.102.0/24 AS6700
195.252.104.0/24 AS6700
ROAs covering this prefix
ROA prefixMax lengthOrigin AS
195.252.64.0/18 /18 AS6700
195.252.64.0/18 /18 AS8400

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is delegated for only 7 of the 10 zones checked.
  • Warning: Reverse DNS is delegated for only 7 of the 10 zones checked.
  • Info: Only the first 10 of 64 reverse zones were checked.
Reverse zones 64
ZoneNameservers
64.252.195.in-addr.arpa ns.beotel.net, ns.beotel.rs
65.252.195.in-addr.arpa ns.beotel.net, ns.beotel.rs
66.252.195.in-addr.arpa ns.beotel.net, ns.beotel.rs
67.252.195.in-addr.arpa ns.beotel.net, ns.beotel.rs
68.252.195.in-addr.arpa ns.beotel.net, ns.beotel.rs
69.252.195.in-addr.arpa ns.beotel.net, ns.beotel.rs
70.252.195.in-addr.arpa Not delegated
71.252.195.in-addr.arpa ns.beotel.net, ns.beotel.rs
72.252.195.in-addr.arpa Not delegated
73.252.195.in-addr.arpa Not delegated
Open in DNS lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameRS-TELEKOM-971112
Handle195.252.64.0 - 195.252.127.255
Range195.252.64.0 – 195.252.127.255
CountryRS
Statusactive
Registered1970-01-01T00:00:00Z
Last changed2025-12-03T09:53:18Z
Abuse contactabuse@telekom.rs
Allocation
Registry (RIR)RIPE NCC
CountrySerbia (RS)
Delegated on1997-11-12
StatusAllocated
Delegated range195.252.64.0/18 (195.252.64.0 – 195.252.127.255)

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

Contacts
RoleNameEmail
registrant TELEKOM SRBIJA a.d.
registrant RIPE-NCC-HM-MNT
registrant TELEKOM-MNT
abuse TELEKOM SRBIJA ABUSE abuse@telekom.rs

Source: https://rdap.db.ripe.net/ip/195.252.64.0/18. 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 Not announced, so there is no origin network to look up.