IPv6 Prefix Bit Membership
Check IPv6 address membership in an explicitly normalized prefix with exact bit arithmetic; no routing or reachability claim.
Description
Check IPv6 address membership in an explicitly normalized prefix with exact bit arithmetic; no routing or reachability claim.
Prefix membership compares address bits with a declared network block, independently of the address's compressed spelling.
When to use this tool
Check IPv6 address membership in an explicitly normalized prefix with exact bit arithmetic; no routing or reachability claim.
- Prepare the supplied address, network, prefix fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter address, network, prefix. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.member. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Normalize network at prefix and return whether parsed address lies between its inclusive start and end.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| address | Address text for the family named by this tool. Prefix lengths are separate fields where shown. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| network | Address text for the family named by this tool. Prefix lengths are separate fields where shown. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| prefix | prefix. | Safe integer |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.member | Membership flag for the specific set and boundary convention above. |
{
"input": {
"address": "::3",
"network": "::",
"prefix": 126
},
"output": {
"result": {
"member": true
}
}
}Limitations and assumptions
- No route, firewall rule, interface assignment or connectivity is inspected.
- IPv4 input uses strict dotted-decimal octets without leading zeros or surrounding whitespace. IPv6 accepts its supported compressed or full spellings and trims surrounding whitespace, but rejects zone identifiers; embedded dotted IPv4 uses the strict IPv4 spelling. IPv6 address outputs are fully expanded unless stated otherwise.
- All declared input fields are required and unexpected top-level fields are rejected. Numbers must be finite; lists are limited to 128 entries and ordinary text fields to 8,192 UTF-16 code units, with tighter limits where stated.
- JSON text inputs must parse within bounded nesting and size limits. Numeric outputs outside the safe finite range are rejected; large exact integer results use decimal strings. Indexes and half-open spans are zero-based unless a rank is explicitly described as one-based.
Alternative or Complementary methods
Use address-set arithmetic for prefix planning and a routing or interface inspection for deployed configuration. Membership and overlap do not establish reachability, ownership or route preference.
References
Similar or alternative tools
- IPv6 Low Bit Field Extractor
Extract an explicitly sized low-bit IPv6 field as decimal integer text, including zero-width zero; no interface-identifier semantics inferred.
- IPv6 Nibble Prefix Length Check
Check IPv6 prefix alignment for whole-nibble reverse-zone labels; nonaligned prefixes do not imply a simple reverse-zone delegation.