An IPv4 address is four octets, so the space is 2³² wide. The workbench answers 4.294967296⋅10+9 — correct, but written with the digits cut off, because its display holds fourteen significant digits and then switches to scientific notation. Open the base converter with FFFFFFFF instead and it prints 4294967295, every digit, because that tool works in integer bases rather than in binary floating point. Two numbers, one address space, and only one of the two screens is exact.
2³² − 1 is 255.255.255.255, the top address, and the whole space is about four billion — less than the world's population, which is the exhaustion problem in one line. Not all of it was ever assignable either: RFC 6890 keeps aside 0.0.0.0/8, 127.0.0.0/8 for loopback, 224.0.0.0/4 for multicast and more, which is why NAT and then IPv6 (2¹²⁸ addresses) followed.
Answer
4.294967296⋅10+9
How to read it
2³² on the workbench, in scientific notation. The base converter prints the same count minus one as 4294967295 in full, since it is not a floating-point value there.
Source
RFC 791 (1981) fixed the 32-bit IPv4 address; IANA's remaining /8 blocks were allocated to the regional registries on 3 February 2011
Work it in the calculator
These links open the right calculator with this problem's numbers already typed in. The line above is what the screen should show — check it yourself.