Skip to content
AdminKit

IP & network

What does the IP & network cluster cover?

AdminKit groups this topic into the IP & network cluster: Your public IP, subnet and routing determine who can reach your connection and how it is addressed on the internet — the starting point for almost every other check on this site.

Glossary (53)

Full glossary →
  • 464XLAT — 464XLAT, defined in RFC 6877, lets an IPv4-only app keep working on a mobile network that only assigns IPv6 addresses, by combining a device-side translator (CLAT) with a provider-side NAT64 gateway (PLAT). AdminKit's My IP tool shows whether a connection is actually IPv6-only, the condition that makes 464XLAT necessary in the first place.
  • Anycast — Anycast is a network addressing technique where the same IP address is announced from many physical locations, and internet routing delivers each client's traffic to the nearest or best-performing instance. AdminKit's DNS Lookup tool queries Cloudflare's public DNS-over-HTTPS resolver, a well-known anycast deployment, on your behalf.
  • ARP (Address Resolution Protocol) — Address Resolution Protocol (ARP), defined in RFC 826, maps a device's IPv4 address to its MAC address on a local network, since hardware needs a MAC address to deliver a frame. ARP has no built-in authentication, which is the basis of ARP spoofing. AdminKit's MAC lookup tool looks up the vendor behind the same MAC address ARP resolves.
  • ARP spoofing — ARP spoofing (ARP poisoning) is an attack on a local IPv4 network where a device sends forged ARP replies claiming to own an IP address belonging to another host, such as the router, letting it intercept or redirect traffic -- a classic man-in-the-middle setup. AdminKit's subnet calculator shows which devices share the broadcast domain this attack depends on.
  • ASN — An ASN (Autonomous System Number) is a unique identifier assigned to a network -- an ISP, cloud provider, or company -- that controls its own block of IP addresses and routing policy on the internet. AdminKit's WHOIS tool looks up the ASN and operator behind any IP or domain, which is often more useful than the registered owner name alone.
  • ASPA (Autonomous System Provider Authorization) — ASPA (Autonomous System Provider Authorization), specified in IETF Internet-Drafts (not yet an RFC), is a signed RPKI object naming the authorized upstream providers of an AS, letting a router reject a BGP path with a forged hop even when its origin looks valid. AdminKit's Whois/RDAP tool checks an IP block's holder and AS number, the relationships ASPA validates.
  • BCP 38 (Source Address Validation) — BCP 38, published as RFC 2827, is the IETF best-practice rule that network operators filter outbound traffic at the network edge, dropping any packet whose source address isn't actually authorized for that network. AdminKit's My IP tool shows your own visible address -- exactly what BCP 38 filtering at your edge stops someone else from forging.
  • BGP announcement — A BGP announcement is a message, defined by RFC 4271, that a network's router sends its neighbors declaring it can route traffic to a given IP block, identified by its ASN. AdminKit's WHOIS lookup shows which network operator and ASN a given IP address's BGP announcements actually point to.
  • BGP community — A BGP community, defined in RFC 1997, is an optional tag a router attaches to a BGP announcement so neighboring networks can apply routing policy -- prefer, de-prioritize, or null-route it -- without a bespoke filter for every case. AdminKit's WHOIS tool looks up the ASN behind a route before checking its community values.
  • BGP hijacking — BGP hijacking is when a network operator falsely announces, via the Border Gateway Protocol, that it owns a block of IP addresses it does not actually control, rerouting other networks' traffic through it. AdminKit's Whois tool checks who actually holds an IP block to help spot a hijack.
  • BGP route leak — A BGP route leak, as RFC 7908 defines it, is a route announcement that propagates beyond the scope its sender, receiver or an AS along the path intended, most often from an accidental misconfiguration rather than a deliberate attack. AdminKit's Whois/RDAP tool looks up the ASN and network operator behind a route, the relationships a leak crosses without authorization.
  • Bogon address — A bogon is an IP address that should never appear on the public internet -- unallocated by IANA, or reserved for private, loopback or documentation use. Firewalls filter bogon traffic as likely spoofed or misconfigured. AdminKit's My IP tool shows your own visible address, which should never itself be a bogon.
  • Broadcast address — A broadcast address is the all-host-bits-set address at the top of an IPv4 subnet, delivering one packet to every device on it at once -- 192.168.1.255 on a /24, for example. AdminKit's subnet calculator works out a subnet's broadcast and network addresses automatically from any CIDR block you enter.
  • CGNAT — CGNAT (Carrier-Grade NAT) is how an ISP shares one public IPv4 address across many customers at once, common on mobile networks, instead of giving each subscriber its own address. AdminKit's My IP tool shows whether your visible address sits in RFC 6598's 100.64.0.0/10 CGNAT range, which affects blacklist status and inbound port forwarding for everyone sharing it.
  • CIDR (Classless Inter-Domain Routing) — CIDR (RFC 4632) is the slash-notation system -- an address followed by a bit count, like 192.168.1.0/24 -- for sizing and routing IP address blocks, replacing the old fixed address classes. AdminKit's subnet calculator takes any CIDR block and works out its network range, mask and usable host count.
  • DHCP (Dynamic Host Configuration Protocol) — DHCP (Dynamic Host Configuration Protocol), defined in RFC 2131, is how a device joining a network automatically gets an IP address, subnet mask, gateway and DNS servers, without anyone typing them in by hand. AdminKit's subnet calculator works out the subnet math a DHCP server's address pool is carved from.
  • DHCPv6 — DHCPv6, defined in RFC 8415, is the IPv6 protocol a server uses to assign addresses and configuration options such as DNS servers to clients, either statefully (assigning the address itself) or statelessly alongside SLAAC. AdminKit's guide to IPv6 SLAAC and EUI-64 addressing explains the self-assignment alternative DHCPv6 is often paired or compared with.
  • DS-Lite (Dual-Stack Lite) — Dual-Stack Lite (DS-Lite), defined in RFC 6333, lets an ISP run an IPv6-only access network while customers still reach the IPv4 internet, tunneling their traffic to a shared carrier-side NAT (AFTR) over IPv6. AdminKit's CGNAT guide compares this with ordinary carrier-grade NAT, which shares addresses without removing IPv4 from the access network.
  • Dual-stack — Dual-stack is a network configuration where a device or network runs IPv4 and IPv6 at the same time, each needing its own security configuration, as defined in RFC 4213. AdminKit's DNS lookup tool resolves both a domain's A (IPv4) and AAAA (IPv6, RFC 3596) records side by side for a dual-stack audit.
  • Dynamic IP — A dynamic IP is a public address an ISP assigns temporarily and can change over time, for example when a DHCP lease expires, unlike a static IP which stays fixed and usually costs extra. AdminKit's My IP tool checks the public address your connection has right now.
  • EUI-64 — EUI-64 derives a 64-bit IPv6 interface identifier from a device's 48-bit MAC address, a format RFC 4291 defines for Stateless Address Autoconfiguration. Because the result embeds a constant, trackable hardware identifier, modern systems now prefer randomized addresses (RFC 4941) instead. AdminKit's guide explains why every IPv6 device still needs its own firewall rules.
  • Happy Eyeballs — Happy Eyeballs, specified in RFC 8305 (updating the original RFC 6555), is an algorithm a dual-stack client uses to race IPv6 and IPv4 connection attempts, keeping whichever completes first rather than waiting for a broken path to time out. AdminKit's DNS lookup resolves both the A and AAAA records that race runs over.
  • IP address — An IP address is the numeric identifier, IPv4 (RFC 791) or IPv6 (RFC 8200), that lets devices find and route traffic to each other, with IPv4's roughly 4.3 billion addresses long since exhausted. AdminKit's IP lookup shows exactly what the internet sees from your connection right now, IPv4, IPv6, or both.
  • IP multicast — IP multicast is a way of sending one packet to every member of an interested group at once, instead of broadcasting to a whole network or sending a separate unicast copy to each recipient. AdminKit's guide to mDNS, SSDP and UPnP LAN discovery covers how those zero-configuration protocols build on multicast to find other devices.
  • IPv4 address exhaustion — IPv4 address exhaustion is the depletion of IPv4's roughly 4.3 billion addresses, reached when IANA allocated its last free blocks to the regional registries in 2011. ISPs responded with Carrier-Grade NAT, sharing addresses from the RFC 6598 reserved block instead of moving networks to IPv6-only. AdminKit's CGNAT guide covers the shared-blacklist tradeoff that mitigation causes.
  • IPv6 — IPv6 is the successor to IPv4, using 128-bit addresses so every device can get its own globally routable address without NAT or CGNAT. Many networks still run IPv4-only firewall rules that never account for a device's IPv6 address, which AdminKit's subnet calculator and DNS lookup tools can help check alongside a device's IPv4 configuration.
  • IPv6 prefix delegation — IPv6 prefix delegation, a DHCPv6 option defined in RFC 8415 (replacing the earlier RFC 3633), lets an ISP hand a router a short prefix -- commonly a /56 or /60 -- to subnet into /64s for its own LANs. AdminKit's SLAAC guide explains how a device turns that delegated /64 into a full address.
  • IPv6 Privacy Extensions (Temporary Address) — IPv6 Privacy Extensions generate a randomized, temporary interface identifier instead of one derived from a device's MAC address, so the same device looks different on every network and over time. AdminKit's guide on MAC address randomization explains why this replaces the older EUI-64 approach for most traffic today.
  • Link-local address — A link-local address is an IP address that only works on its own local network segment and is never routed anywhere else -- IPv6 assigns one automatically in fe80::/10, while IPv4 falls back to 169.254.0.0/16 via APIPA when DHCP fails. AdminKit's guide to IPv6 SLAAC and EUI-64 addressing covers how these get generated and used.
  • Loopback address — A loopback address is the reserved address a device uses to talk to itself -- 127.0.0.1 for IPv4, ::1 for IPv6 -- handled entirely inside its own network stack and never sent over a physical interface. AdminKit's guide to checking for an exposed Redis instance explains why services default to listening there instead of a public interface.
  • MAC OUI — A MAC OUI (Organizationally Unique Identifier) is the first three bytes of a network interface's MAC address, assigned by IEEE to the manufacturer that requested it, which is why looking it up often reveals a device's maker. AdminKit's MAC vendor lookup tool resolves that OUI prefix to its registered manufacturer for exactly this reason.
  • Multipath TCP (MPTCP) — Multipath TCP (MPTCP) extends ordinary TCP so a single connection can use more than one network path at once, such as a phone's WiFi and cellular radios together, instead of staying tied to one address pair for its whole lifetime. AdminKit's My IP tool shows the single address a check sees, even when a connection itself is spread across several.
  • NAT — NAT (Network Address Translation) is how a router lets many devices on a private network share one public IP address, rewriting the address and port on each packet in both directions. AdminKit's CGNAT guide explains the second layer some ISPs add on top, sharing one public address across multiple customers' routers.
  • NAT loopback — NAT loopback (NAT hairpinning) is a router feature that lets a device on a local network reach another local device using its public IP address or domain name, instead of its internal one. Not every consumer router supports it, which AdminKit's My IP tool can help confirm by showing whether your public address even resolves back to your own network.
  • NAT64 — NAT64, defined in RFC 6146, is a stateful mechanism that lets an IPv6-only client reach an IPv4-only server by translating packets at a network boundary, usually paired with DNS64 for address synthesis. AdminKit's CGNAT guide compares NAT64 with the IPv4-side address-sharing technique it's often confused with.
  • NDP (Neighbor Discovery Protocol) — Neighbor Discovery Protocol (NDP), defined in RFC 4861, is IPv6's replacement for ARP, ICMP router discovery and ICMP redirects, using ICMPv6 messages for address resolution and autoconfiguration. AdminKit's SLAAC guide covers how the same Neighbor Discovery messages build a host's autoconfigured IPv6 address.
  • Path MTU Discovery (PMTUD) — Path MTU Discovery (PMTUD) is how a sender finds the largest packet a route's links can carry without fragmenting it, retrying smaller after a router reports its own limit back over ICMP. AdminKit's TLS/SSL check helps tell a stalled handshake caused by a blocked PMTUD message apart from a real certificate problem.
  • PCP (Port Control Protocol) — PCP (Port Control Protocol), defined in RFC 6887, lets a device ask a NAT gateway or firewall to open an inbound port mapping, working across carrier-grade NAT like CGNAT where UPnP alone can't reach. AdminKit's port check tool verifies whether a mapping -- via PCP, UPnP, or manual forwarding -- is actually reachable.
  • Port forwarding — Port forwarding is a router rule that takes inbound traffic on a specific public port and forwards it to a chosen device and port on the local network, which is how a self-hosted service can accept connections from the internet. AdminKit's port check tool confirms whether a forwarded port is actually open and reachable from outside.
  • Regional Internet Registry (RIR) — A Regional Internet Registry (RIR) is one of five nonprofit bodies -- AfriNIC, APNIC, ARIN, LACNIC, and RIPE NCC -- that IANA delegates to allocate IP address blocks and AS numbers within a region, under RFC 7020. AdminKit's WHOIS tool looks up which RIR's registration data a given address or ASN actually belongs to.
  • Reverse proxy — A reverse proxy is a server that sits in front of one or more backend servers and forwards client requests to them, so clients only ever see the proxy's own address. AdminKit's HTTP Headers tool inspects response headers like X-Forwarded-For and Via that often reveal a reverse proxy in the path.
  • RFC 1918 private address — RFC 1918 reserves three IPv4 blocks -- 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 -- for private networks, never routed on the public internet without NAT rewriting the source address at the boundary. AdminKit's subnet tooling helps confirm whether a given address actually falls inside one of these reserved ranges.
  • RPKI ROA (Route Origin Authorization) — An RPKI Route Origin Authorization (ROA), defined in RFC 6482, is a signed object stating which AS number may originate routing announcements for an IP prefix, letting routers validate BGP announcements cryptographically. AdminKit's WHOIS tool shows who holds a block -- the same registry data a ROA's issuer is authorized against.
  • STUN/TURN — STUN (Session Traversal Utilities for NAT) and TURN (Traversal Using Relays around NAT) are protocols that help two devices behind NAT establish a working connection, as WebRTC does for video calls. AdminKit's My IP tool shows the public address and port a STUN server would discover for your own connection, including behind CGNAT.
  • Subnet — A subnet is a logical subdivision of an IP network, defined by a CIDR prefix length like /24 that marks how many address bits identify the network versus the host. AdminKit's subnet calculator works out the usable range, broadcast address and host count for any prefix, and checks whether a given address falls inside it.
  • Supernetting (route aggregation) — Supernetting, also called route aggregation, combines several contiguous, equal-size IP blocks into one larger block advertised as a single route, using CIDR notation defined in RFC 4632. AdminKit's subnet calculator shows a block's boundaries, useful for checking whether adjacent blocks can be cleanly aggregated this way.
  • SYN Cookies — SYN cookies are a server-side defense against SYN flooding, described in RFC 4987, letting a server answer a SYN without allocating per-connection state by encoding what it needs into the SYN-ACK's sequence number, creating real state only once a valid final ACK arrives. AdminKit's protective DNS product applies the same instinct: absorb abuse before it costs server resources.
  • TCP Fast Open (TFO) — TCP Fast Open (TFO), defined in RFC 7413, lets a client send data in the SYN packet of a repeat connection to a server it talked to before, using a server-issued cookie to prove the request isn't forged, saving up to one round trip. AdminKit's port check tests whether a TCP port is reachable before TFO's latency saving even matters.
  • Teredo and 6to4 — Teredo (RFC 4380) and 6to4 (RFC 3056) are legacy IPv6 transition mechanisms that tunnel IPv6 packets inside IPv4 traffic, which can reach a device despite a firewall written with only IPv4 rules in mind. AdminKit's IPv6 firewall guide explains why a device needs its own IPv6-aware rules regardless.
  • ULA (Unique Local Address) — A Unique Local Address (ULA, RFC 4193) is an IPv6 range reserved for private, local-network use, playing a role similar to RFC 1918 private IPv4 ranges. Each site generates its own /48 prefix pseudo-randomly, so independently configured networks rarely collide. AdminKit's subnet calculator computes a ULA block's network range and host count.
  • User-Agent — The User-Agent header is an HTTP request field, defined in RFC 9110, that lets a client identify its software -- conventionally a string naming the browser, its engine and the operating system. It's client-supplied and unverified, so AdminKit's User-Agent tool treats what it parses as a self-reported hint, not a verified fact.
  • VLAN (802.1Q) — A VLAN (Virtual LAN) is a logically separate broadcast domain on a shared physical network, created by tagging Ethernet frames with a VLAN ID per the IEEE 802.1Q standard rather than by physically separate cabling. AdminKit's guide to planning VLANs with a subnet calculator covers assigning each VLAN its own IP range once it is already segmented at this layer.
  • Well-known port — A well-known port -- a System Port in RFC 6335's terms -- is one of the 1,024 numbers from 0-1023 IANA reserves for an established service, like 22 for SSH or 443 for HTTPS. A port number is a strong hint about what's listening, not a guarantee, which is why AdminKit's port-check tool reports what actually answers.

Frequently asked questions

Why does my public IP address keep changing?

Most residential and mobile connections use dynamic IP assignment, where the ISP reassigns addresses from a shared pool on reconnect or lease renewal, and many providers additionally sit behind carrier-grade NAT, so your public IP may even be shared with other customers at the same time (RFC 6598). AdminKit's My IP tool shows the address as seen from the internet side, which is the one that actually changes.

What's the difference between a private IP range and CGNAT?

Private ranges (RFC 1918: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) are reserved for use inside a single network and never routed on the public internet; CGNAT uses a separate reserved block (100.64.0.0/10, RFC 6598) that an ISP uses to share one public IP across many customers at once. Both are non-routable from outside, but CGNAT sits between your private LAN and the real internet rather than inside your own router.

Does my IPv6 address expose my device's MAC address?

Only if the address was generated with legacy EUI-64 interface IDs (RFC 4291), which embed the network interface's MAC address in the low 64 bits — most modern operating systems now generate randomized, temporary interface IDs by default specifically to avoid this. AdminKit's IPv6 info tool flags whether a given address's interface ID looks EUI-64-derived.