Note: Whoever typed it is illiterate because commas go before quotation marks.
The rule about putting commas and such-like inside quotes was promulgated by typographers who cared more about appearance than about substance, more about how words and punctuation look on paper than what the words and punctuation mean. They felt that when you put comma (or period) after a closing quote, the kerning didn't come out right, or at least it didn't if you were assembling the line using movable type slugs, or using a typewriter.
But those of us who care about meaning (and especially among those of us who are programmers, and know that the computer really
cares about meaning) know that quote marks are used to surround a string of text that is to be interpreted literally. That is, you are on-the-fly creating a noun which refers to the very text you construct the noun from.
If comma or period is part of that literal text, then it most certainly belongs inside the quotes. But if not, it most certainly doesn't. In this case, the literal being constructed is the domain name "ax.itunes.apple.com" which, like all domain names does not and cannot contain a comma. The comma is not part of the literal text, and so does not belong inside the quote marks.
And modern computers are quite good at working out the right kerning, thank you very much. We've come a long way since the old days when that rule had any sort of justification. It never made any sort of sense. The proper rule is: put the punctuation inside the quotes if it belongs
inside the quotes; otherwise, leave it outside.
I notice you no longer put two spaces after the period at the end of a sentence. That was another rule from the same era, designed to to overcome the fact that in those days a period didn't kern right. The best remedy was to add enough space after that the unwanted space before wasn't so noticeable. Again, notice that modern computers are quite good at snuggling a period right up against the preceding text, so the double space after is no longer needed.