Ntp_NTPHeader is a JSON Structure definition published by Censys, describing 7 properties. It conforms to the https://json-structure.org/meta/core/v0/# meta-schema.
{
"$schema": "https://json-structure.org/meta/core/v0/#",
"$id": "https://raw.githubusercontent.com/api-evangelist/censys/refs/heads/main/json-structure/platform-ntp-ntpheader-structure.json",
"name": "Ntp_NTPHeader",
"description": "Ntp_NTPHeader schema from Censys Platform API",
"type": "object",
"additionalProperties": false,
"properties": {
"leap_indicator": {
"type": "int32",
"description": "An enumerated value from 0 to 3 signifying whether a leap second will occur at the end of the current month. 0 signifies no leap second, 1 signifies an additive leap second, 2 signifies a subtractive leap second, and 3 signifies the state is unknown.",
"minimum": 0
},
"mode": {
"type": "int32",
"description": "An enumerated value from 0 to 7 signifying the operational mode of the server.",
"minimum": 0
},
"poll": {
"type": "int32",
"description": "The interval within which the server will expect a subsequent synchronization message, in log2 seconds."
},
"precision": {
"type": "int32",
"description": "The precision of the system's clock, in log2 seconds."
},
"reference_id": {
"type": "string",
"description": "The identifier of the reference clock. For servers in stratum 1, one of an IANA-maintained list of sources. For servers in stratum 2, the ID of the stratum 1 server from which the time was retrieved (usually, its IP address), etc."
},
"stratum": {
"type": "int32",
"description": "The number of servers between a client and a non-NTP time source. 1 signifies that the server is authoritative, having direct access to a sensor. 2 signifies that the server got its time from a \"stratum 1\" server, etc. 16 means the clock is unsynchronized.",
"minimum": 0
},
"version": {
"type": "int32",
"description": "The NTP version indicated in the server's response.",
"minimum": 0
}
}
}
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.