Probe 103.149.23.67
← all phase 4 probes · block page · 103.0.0.0/8 map · the record
anomaly in 103.149.23.0/24 (reserved, apnic). Phase 3 saw connect_refused; phase 4 saw connect_refused, and this address answered alone.
Where this address sits
| Block | 103.149.23.0 - 103.149.23.255 (256 addresses) |
|---|---|
| Registry, status | apnic, reserved (not operator-held) |
| RDAP custody | parent object — the registry's answer covers a parent range, 103.0.0.0 - 103.255.255.255 |
| RDAP holder | APNIC-AP · APNIC Hostmaster · ALLOCATED PORTABLE |
| Block UUID | b2d26917-484c-5595-9d51-586034ffdb61 |
| Probes in the block | 54 (4 of them responded, refused, or reset; 0 of 33 measured addresses answered) |
What was observed
| Phase 3 (one GET) | connect_refused, status —, 173 ms |
|---|---|
| Phase 4, port 80 | connect_refused, status —, server —, 0 bytes, digest —… |
| Phase 4, unrelated Host | connect_refused, status —, body different |
| Phase 4, HTTPS | connection_reset, certificate — |
| Certificate names | no certificate was presented |
| Reverse DNS | none |
| Round trips | [183, 184, 183] ms; floor 183 ms, median 183 ms, jitter 1 ms, band none |
The tests, and what each one says here
| Test | Question | Observed | Reading |
|---|---|---|---|
| 1. Registry custody | Does a registry object cover this address? | parent object: the registry's answer covers a parent range, 103.0.0.0 - 103.255.255.255 | The registry has no object for this block: it is inside a parent allocation, so no holder is recorded for these addresses. |
| 2. Ranging (isolation) | Do the two immediate neighbours answer too? | -1 103.149.23.66: timeout, +1 103.149.23.68: timeout | Both neighbours were silent while this address answered: the service is addressed to this address rather than covering a range. |
| 3. Catch-all | Does an unrelated Host header get the same answer? | no page on either Host header (connect_refused / connect_refused) | No page was served, so there is nothing to compare across Host headers. |
| 4. Uniformity | Does the block answer with one page? | Nothing was served, so uniformity cannot be compared. | There is no page to compare, so uniformity gives no signal here. |
| 5. Identity | Do certificate, reverse DNS, and registry agree? | certificate no certificate, reverse DNS no reverse DNS, registry organization APNIC Hostmaster | No certificate was presented, so the only identity evidence is the reverse DNS and the registry record: two layers, not three. |
| 6. Stability | Does it answer the same way on a second pass? | Not measured for this address: the pass has not been repeated. | Stability is one of the discriminators, and a single pass cannot measure it. |
| 7. Distance | Does the smallest round trip sit on a light-speed floor? | floor 183 ms, jitter 1 ms, band none | The smallest of 3 round trips was 183 ms, with 1 ms of jitter. That is below both floors (238.7 ms to geosynchronous orbit, 2564.4 ms to the Moon), so neither distance explains it. |
| 8. Self-explanation | Does the content explain its own purpose? | No content: the address refused, reset, or said nothing. | There is nothing to read, so this test gives no signal. |
| 9. Concealment | Is it silent, inconsistent, or changing? | phase 3 connect_refused, phase 4 connect_refused | The address connect refused rather than answering: something is present and says nothing. That is the shape of a closed port on a host as much as of anything hidden. |
The verdict this probe inherits
Site C: Incidental. Confidence: High.
- The /24 is announced by StarHub, Singapore, so the space is operated even though the registry calls it reserved: a stale record.
- No address serves a page: six refuse the connection and the rest time out, which is ordinary filtering on an announced range where no service runs.
- The geography test passes: 170-181 ms is consistent with the announced operator's location.
What would change it: A page appearing on one of these addresses, or a refusal that moves between passes, would reopen the question.
The layers, as recorded
| Delegation file | see the block page |
|---|---|
| Registry object | parent only (APNIC's 103.0.0.0/8) |
| Routing | AS4657 StarHub Ltd (Singapore), announcing 103.149.23.0/24, first seen not recorded, visibility not recorded |
| Authorization | not recorded |
| DNS pointing here | no reverse DNS |
The verdict is a property of the site, not of this probe: the evidence is block-scale, and no per-address verdict was reached. That is a gap in the work, not a finding about this address.
The full evidence is in the work products (dataflow.out/05_ip_probe_http.json and dataflow.out/06_ip_probe_characterize.json); the registry's verbatim RDAP answer is kept locally and not published.