About this gravatar checker
Compute the identifier used by Gravatar for an email address. The tool trims whitespace around the address, lowercases it and hashes the normalized text with MD5. It displays both the hexadecimal identifier and a 160-pixel avatar URL. These calculations happen locally, so entering an address by itself does not send a request to Gravatar. The result lets you inspect the normalized lookup without automatically contacting the avatar service.
Use the optional preview button to request the generated image from www.gravatar.com. That explicit action sends the address-derived hash and normal network metadata to Gravatar. The URL requests a 404 response when no avatar is available. A failed image load can mean a missing avatar, a blocked connection or a temporary service problem; it cannot conclusively establish that an email account does not exist.
MD5 here is an identifier format chosen by the service, not email encryption. A hash can still be matched against candidate addresses, so treat it as potentially identifying data. This checker does not verify mailbox ownership, send an email or enumerate registrations. Only preview an address when you intend to make that external lookup.
Which controls should I check first?
The Gravatar Checker form labels its controls as Input; Result. Use those labels to keep the source and settings separate. A sample argument that selects a mode is not additional source text. Choose the setting matching your intended operation before copying a result, and change it explicitly when comparing another mode. The labels describe what this form accepts; the worked examples below demonstrate only the stated supplied values.
How should I interpret this specific operation?
The address is trimmed and normalized before its hash is used to build an avatar address. The hash is a representation of the normalized email; it is not proof that a person owns that mailbox. Loading an avatar makes a request to its external host, which differs from calculating the hash locally. Preserve that distinction when interpreting the result and when using a real email address.
Worked helper values
These values come from the reproducible calculation examples supplied with this tool. Each row identifies the complete supplied arguments and the returned value. A visible ↵ denotes a line break and ⇥ denotes a tab in text examples. Settings appear alongside source data so that a different mode is not mistaken for an identical input. These are helper calculations, not observations of a live device, fetched target, image decoder, browser preview or downloaded file. Use the stated method above to relate the returned fields to the actual operation.
| Supplied values | Calculated return value |
|---|---|
| [email protected] | {"hash": "0bc83cb571cd1c50ba6f3e8a78ef1346", "url": "https://www.gravatar.com/avatar/0bc83cb571cd1c50ba6f3e8a78ef1346?s=160&d=404"} |
What is supplied data and what is an inference?
The input is a supplied record, string or local file. The output can divide that data into fields or infer likely labels using documented rules. Keep the exact source with the result so that another person can check the interpretation. A parsed field is not automatically a verified fact about the outside world. A user-agent string can be changed, a metadata tag can be edited, and an extracted address can be unavailable. Preserve unknown or missing fields rather than filling them with plausible values that were never present in the source.
Why should I inspect related fields together?
A single label can conceal ambiguity that other fields make visible. A URL has a host, path, query and fragment; a file can have a filename, claimed media type and byte signature; photo metadata can have several different dates. Keep those distinctions in the report rather than collapsing them into one convenient summary. Compare each value with the kind of source it describes. A file extension does not define its actual byte format, and a date stored in an editable tag is not an independent measurement of when the picture was created.
How do I handle absent information?
Treat an absent field as absent. It can mean that the source never contained the information, that its format does not support it, or that the parser did not recognize it. An empty text field can also differ from an omitted field. Read any status message before inferring that the entire input failed. If the result depends on rules or a supported format list, compare a minimal recognized example first. Add a precise note about the missing source value instead of inventing a device model, owner, timestamp or destination based on surrounding clues.
What does the helper example verify?
The example supplies all of its input values explicitly and reports what the local function returned. That demonstrates parsing, normalization or field preparation for those values. It does not verify a device, fetch a website, prove file safety or authenticate metadata. The distinction remains even when an output label resembles a factual statement. A parsed browser family, for instance, comes from the supplied text rather than contacting that browser. Read the example as a reproducible interpretation of data and use separate evidence for claims about the actual external source.
How can I make a comparison reproducible?
Save the original input, parser settings and complete output fields relevant to the question. If the source is a file, keep an untouched copy instead of relying only on its reported filename. If it is a string, retain its punctuation and whitespace. Change one preparation step at a time, such as trimming surrounding spaces or choosing a decode direction, and compare the affected fields. That makes a mismatch traceable to a rule rather than to a guessed environmental change. Avoid sharing real credentials or private metadata in a demonstration sample.
Is the address sent on typing?
No. The local calculation only prepares a URL.
What happens on preview?
An image request carrying the address-derived hash is sent to www.gravatar.com.
Does a failed preview mean no account exists?
No. It can also indicate a network block or service error.