So ... you're doing Web design, and you've heard all about responsive design, and you're reading the W3.org CSS3 docs, but you're stuck trying to figure out just what exact properties the device you're targeting has ... or thinks it has.
I couldn't find such a thing. So I made it.
* CodePen: http://codepen.io/dredmorbius/pen/NPJVVz
* HTML: http://pastebin.com/KSn8FwUP
* CSS: http://pastebin.com/AARf3TwY
Oh, and one of the discoveries as a consequence: my aged Android device was ... being curiously overzealous in trying to render large-resolution rather than more modest ones of my Webpage design. I'd already had a set of queries for sizes ranging from 35 - 85rem (the "rem" is a "root em", where an "em" is a typographic unit of measure equal to the width of an 'm' character -- basically it's a question that asks "how much text can I fit on a line stretching across your screen"), and I knew it was shooting for the largest. But ... why? So I threw a larger range of values ... and was still getting like total redic responses (32,768 rem). That happens to be one of a few standard breakpoints in computer numbering (2^15 or signed 2^16 integers). So I tried values up to 2^64 (a really big integer). Android still said "send me more". I gave up at 2^128, a display size which would be ... large. Cosmologically large.
But I figured I had to reflect that in my report. So Skeptical Kid makes an appearance...
And this is why I Am Not a Web Designer.... Who the fuck ships a browser (and supports it for years) that 1) answers CSS media queries in rem, but 2) gives the wrong fucking answers.
This is also why I fear the Internet of Broken Things.