Copy the URL without opening it where possible. Identify subdomains, subtle misspellings, lookalike characters, shorteners and tracking parameters.
2
Verify the claimed identity
Compare legal name, address, contacts, required notices and payment details with appropriate official sources.
3
Reconstruct public history
Review accessible registration traces, certificates, archives and content changes. A recent domain is not proof of fraud, but it changes confidence.
4
Observe public relationships
Look for related domains, redirects, official profiles, advertising and warnings from identifiable sources.
5
Assess the requested journey
Consider whether the site asks for credentials, payment, software, documents or urgent action. More sensitive requests require more independent verification.
6
Decide without further interaction
Classify the site as coherent within the observed scope, doubtful, avoid or undetermined. Continue a legitimate task only from an independently found official site.
A domain is an identifier, not decoration
The meaningful part of a URL can be hidden behind a long subdomain or reassuring phrase. Verify the registered domain and extension, then restart from a known official source.
HTTPS protects data in transit to the visited site; it does not certify the business, offer or intention.
Look for overall coherence
A site can copy text, logos and reviews. Compare contacts, history, legal pages, official channels, payment methods and independent presence.
One anomaly deserves checking; several independent inconsistencies combined with urgency or a sensitive request justify stopping.
Research without unnecessary exposure
Do not install a file, allow notifications, enter data or call the supplied number before legitimacy is established.
Professional review should use an appropriate environment and clear mandate. This guide remains limited to defensive public observation.
What a certificate can date
Record covered names and certificate validity bounds. They date neither company formation nor necessarily first publication. Renewal does not establish an operator change. Compare the actual visited hostname with independently obtained details.
Verify the operator without testing a transaction
Compare site notices, registered entity, contact and offer terms. A real company may be named without permission. Do not buy or submit documents to test trust. Name the unresolved issue: entity existence, website connection or transaction authority.
Reading technical evidence
Date an RDAP event rather than a website’s activity
An RDAP response pairs an event type with a date. Retain both fields together.
Field or situation and its interpretation
Observed item
What it means
eventAction: registration
Registration event for the object; it does not date the website’s first publication.
eventAction: last changed
A change to the registered object; it does not prove a change of owner.
eventDate
Read the date with its UTC offset and the response consultation date.
Record the exact domain and queried service. Corroborate the operator’s identity and publication history separately.
For each point, record what the material actually supports. “Supported” applies to the specific observation, not to the entire case. A contradiction needs explanation; missing material remains an open question.
Define the question
Record the source
Test the observation
State the limits
Entries stay in this page until you leave or reload it. Nothing is saved or submitted by this tool. Use neutral references instead of personal data or credentials.
How to write a useful conclusion
Editorial examples, not findings about your case
Material
Useful wording
Next check
One dated source
The consulted source stated X on the recorded date.
Check its origin and whether it still applies.
Multiple copies of one claim
Several pages repeat X; independent corroboration is missing.
Find the original and a source with independent evidence.
Conflicting sources
A states X while B states Y; the difference is unresolved.
Compare dates, scope, identifiers and definitions.
No matching result
No result was found in the recorded scope.
Describe queries, coverage and access limitations.
What to check and what to record
Use this grid to turn the method into a reviewable case file. A missing item remains an open question. The interpretation limit prevents a finding from becoming an unsupported conclusion.
Topic-specific checks
Check
Useful record
Interpretation limit
Domain name
Exact name, lookalike characters, RDAP date and registrar.
Redacted ownership or a recent domain does not establish fraud.
Certificate
Covered name, validity period and dated observation.
HTTPS protects transport without guaranteeing the merchant.
Merchant contact
Legal identity and a contact found outside the suspect site.
A real company can be impersonated.
Common pitfalls
Four shortcuts that weaken the result.
Trusting the padlock
HTTPS encrypts the connection but does not guarantee legitimacy.
Testing with false details
Interaction may confirm that your address or device is active.
Believing embedded reviews
They can be selected, copied or fabricated. Find the source and date.
Making an unsupported accusation
Preserve observable facts and use proportionate language.
Practical questions
Frequently asked questions.
Is a new domain fraudulent?
No. It is a contextual signal to compare with identity, journey, content and other sources.
Does HTTPS prevent phishing?
It protects transport to the domain visited, including a domain controlled by a fraudster.
How can I check without clicking?
Inspect the address, research the organisation separately and use suitable public tools without submitting data to the site.
Public references
These primary references support the checks described here. The sequence and working sheet are an IIS editorial method; a cited organisation does not endorse this guide. Read each reference within its stated date, jurisdiction and scope.
ICANN — RDAP. Official context for domain registration lookup and its limits.
RFC 5280. Reference for the technical fields and interpretation boundaries described in this guide.
Editorial scope
Published by Internet Intelligence Service on 15 September 2026. Last content update: 29 October 2026. This educational guide describes a lawful, defensive method. It is not legal advice, an emergency service or authority instruction.