Someone in your lobby claims they can "pull your IP" and boot you offline. Here's what's actually possible on Xbox and PS5 in 2026, and the five settings that shut it down for good.
Xbox & PS5 IP Puller: How It Actually Works and How to Stop Anyone From Getting Your IP (2026)
Someone in your lobby says "I've got your IP, watch what happens." Then your connection drops mid-match. Coincidence, or did they actually pull it?
Someone in your lobby says "I've got your IP, watch what happens." Then your connection drops mid-match. Coincidence, or did they actually pull it?
Short answer: on modern consoles, probably not the way they're implying — but the older method still works often enough that it's worth locking down. Here's what's real, what's bluffing, and how to make sure your address never shows up in one of these databases in the first place.
What an IP puller actually is
An IP puller (also called a resolver, sniffer, or grabber) is software that captures the IP addresses of other players connected to the same online match. Tools like Xresolver, OctoSniff, and Lanc Remastered PCPS have circulated in gaming communities for years, mostly tied to Xbox Live and PlayStation Network lobbies.
They work in one of two ways:
Packet sniffing. During peer-to-peer (P2P) connections — most commonly party chat and some older game lobbies — your console exchanges data directly with other players' consoles instead of routing everything through a game server. A packet sniffer sitting on the network can read the source and destination IPs in that traffic. This is how tools like Lanc Remastered have worked since the Xbox 360 era.
Gamertag databases. Sites like Xresolver don't sniff anything live — they query a stored database. Every time someone's IP got pulled once, it may have been logged against their gamertag. Type in a tag, get a historical IP. Microsoft has sued over this at least once (Xresolver briefly went dark in August 2020 before returning), but the database model keeps resurfacing under new domains.
Why this still works in 2026
Most modern game traffic runs through dedicated servers, not P2P — so a straight packet sniff during ranked matchmaking usually won't expose you. Party chat is the exception. Xbox party chat and PlayStation's older party system route voice traffic peer-to-peer by default in a lot of regions, which means the moment you join a call with a stranger, your console and theirs are talking directly.
That's the actual attack surface. It's not "they hacked into your Xbox." It's "you joined a P2P voice call with someone running a sniffer."
Is this actually dangerous?
Depends what happens next. Realistically:
- Booting/lag switching. The main use case. Someone floods your IP with traffic (a DDoS, dressed up as a "boot") to disconnect you or force lag, usually to win a match or settle a grudge from chat.
- Rough geolocation. An IP resolves to a city or metro area, not a street address. Annoying, not doxxing on its own.
- Follow-up targeting. The real risk isn't the IP itself — it's what someone does with it combined with other info you've dropped in chat (your city, your schedule, your school).
You can check what your own IP currently reveals — location accuracy, ISP, connection type — at tracemyiponline.com/ip-lookup. It's the same data a resolver database would be showing about you.
How to stop it — Xbox
Turn off P2P party chat where possible. Xbox doesn't give you a single global toggle for this, but you can control who you're exposed to:
- Go to Settings → Account → Privacy & Online Safety → Xbox Live Privacy → View Details & Customize.
- Under Communication & Multiplayer, set "You can talk to and hear voice chat from" to Friends or Friends of Friends instead of Everybody.
- This alone kills most cold-lobby exposure — strangers in your match can't pull you if they can never party-chat with you.
Use a VPN for console traffic. Routing your Xbox through a VPN (via a router-level VPN or a shared PC connection) means any packet sniff resolves to the VPN's IP, not your home IP.
Enable NAT strictness intentionally. Counterintuitively, a Strict NAT type reduces the number of direct P2P connections your console makes, which cuts down sniffing opportunities — at the cost of matchmaking speed. Worth it if you're being targeted repeatedly.
How to stop it — PS5
- Settings → Users and Accounts → Privacy → Personal Info / Messaging, restrict who can send voice/party invites to Friends.
- Disable Party Chat with strangers entirely if you play with a fixed squad.
- Same VPN logic applies — a home-router VPN protects every device on the network, console included, without per-device setup.
If you think you're already in a resolver database
Sites like Xresolver historically offered opt-out/blacklist forms — check the current resolver site you're worried about for a removal request process. It won't undo a leak, but it stops future lookups against your tag. Beyond that, the practical move is changing your home IP: most ISPs will reassign a dynamic IP if you request it, or you can reboot your modem and leave it unplugged for 10+ minutes, which forces a new lease with most residential ISPs.
"The mistake I see constantly is people treating console IP exposure like it's equivalent to a home address leak," says Marcus Webb, a network security consultant who has audited gaming platform infrastructure for esports orgs. "It's a data point, not a doxx. The actual damage almost always comes from combining it with something the player said out loud in chat — their city, their routine, their school. Lock down party chat and you've closed 90% of the realistic exposure."
Xbox vs PS5: exposure comparison
XboxPS5Default party chat routing | P2P in many regions | P2P for older party system; some titles use relay
Privacy control granularity | Per-category (Friends/Friends of Friends/Everybody) | Similar, under Personal Info & Messaging
Known resolver targeting | High (Xresolver historically Xbox-focused) | Moderate, growing
Fix without buying anything | Restrict chat to Friends | Restrict chat to Friends
Privacy control granularity | Per-category (Friends/Friends of Friends/Everybody) | Similar, under Personal Info & Messaging
Known resolver targeting | High (Xresolver historically Xbox-focused) | Moderate, growing
Fix without buying anything | Restrict chat to Friends | Restrict chat to Friends
FAQs
Can someone really get my IP just from playing against me? Not in most modern matchmaking, since that traffic runs through game servers. Party chat is the main exposure point because it's often peer-to-peer.
Does a VPN slow down my console gaming? Some, depending on server distance and VPN quality. A nearby VPN server with a gaming-friendly provider usually adds single-digit milliseconds — noticeable in competitive shooters, rarely a problem otherwise.
Is using an IP puller against someone illegal? Collecting a public IP isn't illegal by itself in most jurisdictions. What someone does with it — a DDoS attack, harassment, stalking — is illegal in the US, UK, Canada, and Australia under existing computer misuse and harassment laws.
Will changing my gamertag stop resolver lookups? It stops lookups against the old tag going forward, but any IP already logged against it stays in that database's history.
Does turning off cross-play help? Not directly for IP exposure — cross-play affects who you're matched with, not how party chat routes.
Can my ISP see that someone tried to pull my IP? No, they can only see traffic patterns, not intent. If you're hit with a genuine DDoS, your ISP may flag the traffic spike, but they won't identify who ran the puller.
Does Strict NAT actually protect me, or just annoy me? Both, honestly. It reduces P2P connections (protective) but can cause matchmaking issues and party chat problems in some games.
Should I report resolver sites to Microsoft or Sony? Yes — both platforms have abuse-reporting channels, and Microsoft has taken legal action against resolver operators before. Reporting contributes to that pattern even if it doesn't get an individual site removed instantly.
Check your exposure now
See exactly what your current IP reveals — location accuracy, ISP, connection type — the same way a resolver database would log it. Free lookup at TraceMyIPOnline.com/ip-lookup. If it looks exposed, run it through our VPN detector after setting up protection to confirm it's actually masked.