INFO: Accessible NTRIP Report

DESCRIPTION LAST UPDATED: 2025-08-26

DEFAULT SECURITY LEVEL: INFO

This report contains hosts that respond to NTRIP (Networked Transport of RTCM via Internet Protocol) probes on 2101/TCP. From Wikipedia: The Networked Transport of RTCM via Internet Protocol (NTRIP) is a protocol for streaming differential GPS (DGPS) corrections over the Internet for real-time kinematic positioning. RTCM SC-104 is a communication protocol for sending differential GPS (DGPS) to a GPS receiver from a secondary source like a radio receiver. The standard is named for the Special Committee 104 of the Radio Technical Commission for Maritime Services (RTCM) that created it..

You can view an overview of version 1.0 of the NTRIP protocol here: https://gssc.esa.int/wp-content/uploads/2018/07/NtripDocumentation.pdf

NTIP Version 2.0 is proprietary. You can find an open source implementation at https://software.rtcm-ntrip.org/.

Our scan locates accessible NTRIP Caster servers. These will often be intentionally publicly available. We share the information for awareness purposes only. We do not check any vulnerability related information. Network owners should be aware of the provision of such services on their network and on any accessibility issues.

You can track exposed NTRIP servers on our Dashboard.

Severity levels are described here.

For more information on our scanning efforts, check out our Internet scanning summary page.

This report has an IPv4 version.

Filename(s): population_ntrip

Fields

  • timestamp
    Timestamp the event occured in UTC+0
  • severity
    Severity level
  • ip
    IP of the device
  • protocol
    Protocol (TCP)
  • port
    Port of the service
  • hostname
    Reverse DNS name of the device in question
  • tag
    Additional tag information - will be primarily ntrip
  • asn
    ASN of where the device in question resides
  • geo
    Country where the device in question resides
  • region
    State / Province / Administrative region where the device in question resides
  • city
    City in which the device in question resides
  • naics
    North American Industry Classification System Code
  • hostname_source
    Hostname (either from DNS or SSL cert)
  • sector
    Sector to which the device belongs to
  • ntrip
    Sourcetable response
  • ntrip_code
    Response code: e.g., 200, 401, 404
  • ntrip_reason
    The text reason to go with the NTRIP Code
  • content_type
    The MIME type of the body of the request (used with POST and PUT requests)
  • connection
    Control options for the current connection and list of hop-by-hop request fields
  • server
    NTRIP Server type
  • content_length
    The length of the response body in octets
  • ntrip_version
    Version of NTRIP in use
  • ntrip_date
    Timestamp returned by NTRIP server
  • ntrip_type
    Indicator of a stream description (either STR, CAS, or NET) We are parsing STR type records
  • mount_point
    Datastream Mountpoint
  • identifier
    Source Identifier - this is often the city nearest the device
  • format
    Generic description of the type of data that the device can stream (BINEX, CMR, NMEA, RAW, et cetera)
  • format_details
    Specifics on the type of data presented in the format field
  • carrier
    Phase information, if the data stream contains GNSS measurements/correction
  • nav_system
    Navigation Systems supported (BDS, GAL, GLO, GPS, IRS, QZS, SBAS)
  • network
    Network Name
  • ntrip_country
    ISO 3166 country code
  • ntrip_latitude
    NTRIP device position, Latitude in degree
  • ntrip_longitude
    NTRIP device position, Longitude in degree
  • nmea
    Caster requires NMEA input (1/0)
  • solution
    Generated by a single base (0) or network (1)
  • generator
    Generating software or hardware name
  • compression
    Compression algorithm in use
  • authentication
    Access protection for Data Streams: None (N), Basic (B), or Digest (D)
  • fee
    User fee for data access: yes (Y) or no (N)
  • bit_rate
    Data rate in bits per second
  • misc
    Miscellaneous information
  • header_base64
    Raw NTRIP response headers encoded in base64
  • body_base64
    Raw NTRIP response body encoded in base64

Sample

"timestamp","severity","ip","protocol","port","hostname","tag","asn","geo","region","city","naics","hostname_source","sector","ntrip","ntrip_code","ntrip_reason","content_type","connection","server","content_length","ntrip_version","ntrip_date","ntrip_type","mount_point","identifier","format","format_details","carrier","nav_system","network","ntrip_country","ntrip_latitude","ntrip_longitude","nmea","solution","generator","compression","authentication","fee","bit_rate","misc","header_base64","body_base64"
"2010-02-10 00:00:00",info,192.168.0.1,tcp,2101,node01.example.com,ntrip,64512,ZZ,Region,City,0,ptr,"Communications, Service Provider, and Hosting Service",SOURCETABLE,200,OK,gnss/sourcetable,,"NTRIP Caster 1.0",32,Ntrip/1.0,"12/18/2023:20:10: 1 GMT",STR,RTCM3,,"RTCM 3.0",RTCM(1),2,GPS+GLONASS,,SE,55.52,13.09,0,0,"Trimble SPS850",,B,N,9600,,co6R8kL1Tru4g9L//hZTvA==,TiHCFOxH38FzjkhEUfLmgBSysiyEfp/Fh/XFO46U+VU=
"2010-02-10 00:00:01",info,192.168.0.2,tcp,2101,node02.example.com,ntrip,64512,ZZ,Region,City,0,,"Education Services",SOURCETABLE,200,OK,text/plain,,"GNSS Spider 7.8.1.9468/1.0",32,,"lun, 18 dic 2023 20:09:42 GMT",STR,RTK2,RTK2,"RTCM 2",,2,GPS+GLO,,,37.82,15.01,1,0,"Leica GNSS Spider",none,N,Y,9600,^M,SDbE1s4KWvY3IXGGSoN5kg==,E9SAnbWaDQQFVwVQZImU8XFlrhQsyiXKGWfbrkINMBo=
"2010-02-10 00:00:02",info,192.168.0.3,tcp,2101,node03.example.com,ntrip,64512,ZZ,Region,City,0,,,SOURCETABLE,200,OK,text/plain,close,"NTRIP BDStarCaster/1.0",32,,"Mon, 18 Dec 2023 20:09:42 GMT",STR,TPGE3,BDStar,RTCM3,"1057(5),1058(5),1059(5),1265(5)",2,GPS,,CHN,1.23,4.56,0,1,YYY,none,N,N,1000,none^M,aZ4xb3NVjprh7GUe0AMMnA==,SLz17YWndPs8rE6h7Rxo58kOCwplALZSaRP9ClfUN4s=

Our 137 Report Types

« Back to Network Reporting