Services · resolution
Identity resolution
By analyzing hundreds of millions of successful email opens from the RampedUp Email Exhaust Exchange, we assign IP addresses to corporate domains — then verify the result against the ARIN registry and a DNS lookup. Each association carries a LOW, MEDIUM or HIGH confidence score.
Two resolutions, both cookie-free: a hashed email back into a full contact profile, and an IP address back to the company behind it. Fewer than 10% of IP addresses are registered to the company actually using them, which is why a registry lookup on its own so rarely identifies a visitor.
HEM resolution
Hashed emails resolve into full contact profiles.
A hashed email address — a HEM — is an anonymized key. On its own it identifies nobody. Matched against the RampedUp file it resolves back into a full contact profile: name, standardized job title, function and title level, current employer, and the firmographics attached to that employer.
We accept HEMs as a data appending input. Send a file of hashed emails the same way you would send a file of plain addresses, and get back the resolved records — see data appending for how the match runs and what comes back.
HEM in, profile out
The hash is the join key. You never have to hand over a plain-text email address to get the record behind it.
An appending input like any other
HEMs sit alongside email, name plus domain, and company as accepted match keys. Credits are spent on matches, not on rows submitted.
The reverse of the Ad Tech file
The Global Ad Tech file is keyed on an MD5 hash of the personal email across 197,417,818 records. HEM resolution is that relationship run the other way.
Working from an audience you cannot de-anonymize yourself — an onboarded segment, a partner list, an ad platform export — is the usual reason to need this. Tell us which hash you hold and we will confirm the match before you commit. [CONFIRM SUPPORTED HASH ALGORITHMS]
Two directions, one association
Email open IP
The known IP addresses associated with a domain, returned as an array with a confidence score based on signal strength and how uniquely the domain maps to the IP.
Domain to IP
Input a domain, receive the associated IP addresses. Multiple IPs per domain are available, which is what makes visitor identification workable in practice.
Why confidence is scored, not asserted
An IP-to-company match is probabilistic. A shared office building, a consumer ISP range, a VPN exit — all produce associations that look real and are not. Scoring the confidence LOW, MEDIUM or HIGH lets you decide which matches are good enough to route to a salesperson and which are only good enough for an aggregate report.
Verification against the ARIN registry and a DNS lookup is the cross-check on top of the behavioral signal.
This is company-level identification, not person-level. It tells you an organization visited, not who.
Take a Deeper Dive into the Knowledge Base
Step-by-step articles and how-tos from the RampedUp Knowledge Base.
There’s an API for that
Everything on this page is also an endpoint. Searching and counting never decrement credits.
Append Contact Details, Company Details and Validate Email Address for ONE contact at a time. Real-time results, no queues. For Identity Resolution, ensure the HEM is lowercase using our "md5HashedEmailAddress" endpoint.
Endpoint
Manual_Append/post_manualappend_contact
Open Real-Time Contact Append in the Swagger portal All endpoints
Start with the number.
Tell us the segment you actually sell to and we will send the exact count, the fill rates for that slice, and a sample — before anyone asks you for a budget.