On 2026-10-01, an HTTP check of ormanandco.com returned status 502, a recorded server response rather than a statement about the site's content. The domain was first observed on 2026-09-13, and its registration date is listed as 2026-05-28.
Recorded Evidence
The HTTP check on 2026-10-01 returned status 502. A VirusTotal check on 2026-09-21 recorded 5 detections across 89 scanners. An OTX check on 2026-09-21 recorded 1 pulse. The domain appears in the PhishDestroy internal listing, and the blocklist check was performed on 2026-10-01. The registrar is listed as PDR Ltd. d/b/a PublicDomainRegistry.com, and the IP address 216.150.16.193 is recorded in the US.
Interpretation
The HTTP 502 response and the VirusTotal and OTX records describe separate observations made on their own dates, so they should be read as distinct data points rather than a combined signal. The gap between the first observation and the later checks shows the domain has been tracked across multiple dates, but the records do not establish what changed between them. The PhishDestroy internal listing is a publisher-owned catalogue entry and does not by itself confirm any behavior.
Recommended Actions
Preserve the HTTP response record for ormanandco.com and the PhishDestroy internal listing entry for future comparison. Separately retain the VirusTotal and OTX records so each source can be reviewed on its own terms. Compare future checks of ormanandco.com against these saved records to see whether the recorded responses and source observations remain consistent.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='ormanandco.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 13, 2026
Page Title
Orman & Co Limited
TLS Certificate
Hostname coverage not recorded·
Issued by YR2
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
216.150.16.193
Network ASN
AS16509
Observed location
US
Server header
Vercel
Edge-IP reputation is not attributed to this domain.
Nameservers 1
wesley.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
YR2
Hostname coverage
Hostname coverage not recorded
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:30:24 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-13 05:28:07 UTCcurrent episode first observed: 2026-09-30 16:26:51 UTCobserved RIP window: 2026-09-13 05:28:07 UTC → 2026-09-30 16:26:51 UTC · 418.98hmidpoint estimate ≈ 2026-09-21 22:57:29 UTC · precision low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
ormanandco.com detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 20, 2026
Time to First Unavailability
161 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
4 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · ormanandco.com
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(US)
