What does risky mean? Risky means the address is not confidently invalid, but sending still carries enough uncertainty that you should make a policy decision instead of treating it as clean. Common risky patterns Risky outcomes often involve: - provider ambiguity - catch-all behavior - signals that are not strong enough for certainty Recommended next step Treat risky as a review state. Do not merge it automatically into valid. Read Results and Statuses for a fuller decision framework. If you need a recommended send policy, open the support widget and describe the campaign type.
Why did verification return unknown? Unknown means the system could not establish enough certainty at the time of the check. Why this happens Typical reasons include: - temporary provider behavior - greylisting - inconclusive server responses - conditions that need a retry instead of a forced answer What to do - avoid treating unknown as valid - retry later if timing matters - review whether the address source is high quality For the deeper explanation, read Results and Statuses. If unknown results persist unusually long, open the support widget with the job ID or domain examples.
Why did a list take longer than expected? Large or complex lists can take longer when the job hits provider throttling, temporary uncertainty, or deeper network checks. Normal causes of slower processing - large file size - greylisted or ambiguous domains - provider throttling - temporary network variability What to check Look at the job status and progress first. If progress is moving, the system is usually still working through the queue correctly. If the job appears stuck, capture the job ID before contacting support. Use Results and Statuses to understand why some domains take longer to resolve. Open the support widget with the job ID if the run looks stalled rather than just slow.