Private digital intelligence bureau Lawful OSINT · Cyber monitoring · Due diligence
Researcher reconstructing the ownership and public history of a suspicious website

Web fraud guide · 11 min

Check a suspicious website without clicking through everything or mistaking polish for legitimacy.

A padlock, professional design or high search position does not establish trust. Start with the exact address, claimed entity and observable history.

Published Updated Publisher and method: IIS

At a glance

Four rules for a useful review.

  • Read the address character by character.
  • Do not submit data as a test.
  • Compare identity, domain and history.
  • Preserve redirects and observed pages.

Step-by-step method

A reproducible path from question to conclusion.

  1. 1

    Isolate the exact address

    Copy the URL without opening it where possible. Identify subdomains, subtle misspellings, lookalike characters, shorteners and tracking parameters.

  2. Laptop, phone and notebooks on a desk — AI-generated photograph
    2

    Verify the claimed identity

    Compare legal name, address, contacts, required notices and payment details with appropriate official sources.

  3. Two colleagues preparing content at an accessible table — AI-generated photograph
    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. 4

    Observe public relationships

    Look for related domains, redirects, official profiles, advertising and warnings from identifiable sources.

  5. 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. 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 itemWhat it means
eventAction: registrationRegistration event for the object; it does not date the website’s first publication.
eventAction: last changedA change to the registered object; it does not prove a change of owner.
eventDateRead 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.

RFC 9083, § 4.5

Worked example

A shop displays HTTPS and a real company’s details

Fictional teaching case, not a client investigation.

Do the visible details connect this shop to the company it claims to represent?

Observation, interpretation and limit
ObservationWhat it establishesWhat remains unproven
The address uses HTTPS and the page displays a company number.The site presents an encrypted channel and a claimed identifier.Encryption and a copied number do not establish permission to operate the shop.
The register confirms a namesake company, whose published website uses another domain.The identified entity exists and another address is published.A legitimate secondary site or an old address remains possible.
The sales team reached independently cannot confirm the shop.The relationship between shop and company remains unestablished.Lack of confirmation does not identify the actual operator.

Conclusion to record

The shop’s legitimacy is unresolved. Defer payment and document transfer; keep the URL, displayed terms and independent verification outcome.

What would change the conclusion?

Review if an official channel explicitly confirms the domain and the payment pathway concerned.

Check your reasoning

A valid certificate answers a technical question. List the commercial and identity questions that remain open.

· Open the verification log

Your working sheet

Turn the method into a documented review.

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.

  1. Define the question
  2. Record the source
  3. Test the observation
  4. 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.

1. Domain name

Exact name, lookalike characters, RDAP date and registrar.

Limit: Redacted ownership or a recent domain does not establish fraud.

2. Certificate

Covered name, validity period and dated observation.

Limit: HTTPS protects transport without guaranteeing the merchant.

3. Merchant contact

Legal identity and a contact found outside the suspect site.

Limit: A real company can be impersonated.

How to write a useful conclusion
Editorial examples, not findings about your case
MaterialUseful wordingNext check
One dated sourceThe consulted source stated X on the recorded date.Check its origin and whether it still applies.
Multiple copies of one claimSeveral pages repeat X; independent corroboration is missing.Find the original and a source with independent evidence.
Conflicting sourcesA states X while B states Y; the difference is unresolved.Compare dates, scope, identifiers and definitions.
No matching resultNo 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
CheckUseful recordInterpretation limit
Domain nameExact name, lookalike characters, RDAP date and registrar.Redacted ownership or a recent domain does not establish fraud.
CertificateCovered name, validity period and dated observation.HTTPS protects transport without guaranteeing the merchant.
Merchant contactLegal 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.

Two phones and a backup device before changing devices — AI-generated photograph

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.

Find primary portals and their limitations

Editorial responsibility, examples and corrections