DNS Resolvers Are a Path, Not an Identity
The resolver is who the operating system asked. It can disagree with the TCP source, the JS timezone, and the User-Agent, and all of those answers can still be true.
Read articleResources Center
Knowledge material for technical stakeholders exploring Fraudnode workflows.
Articles
Search by tags, filter by section, and navigate research notes by topic.
Search
10 results
Sections
Tags
The resolver is who the operating system asked. It can disagree with the TCP source, the JS timezone, and the User-Agent, and all of those answers can still be true.
Read articleSETTINGS, pseudo-header order, and the first HEADERS frame are chosen by the client library. That is why HTTP/2 still identifies a stack after the TLS handshake is over.
Read articleWhy mobile fraud detection must preserve continuity across device state, app profiles, network signals, behavior, and transaction history.
Read articleThe 16-bit window is not the real window. RFC 1323 freezes a scale factor on SYN, and some stacks still set the raw window to a multiple of MSS.
Read articleWhy Layers 3 through 7 still define how modern anti-fraud and security detection works.
Read articleMaximum Segment Size is not a device ID. It is a receipt for every header, tunnel, and radio hop between the client and the collector.
Read articleOn masking, infrastructure trust and why detection is shifting below the surface.
Read articleFrom BIOS to system calls, a practical map of what "Linux" actually is and where the kernel ends.
Read articleHow pod networking, CNI plugins, and service mesh components work together in Kubernetes.
Read articleA practical, layer-by-layer tour of DNS, TCP, TLS, BGP, CDN, backend infrastructure, and browser rendering through the life of one web request.
Read article