security-server-landing-page--obipsalms.replit.app returned HTTP status 200 on 2026-10-03, according to the recorded HTTP check. A Google Safe Browsing check dated 2026-09-30 flagged the domain for social engineering, and PhishDestroy's internal listing also records it.
Recorded Evidence
The HTTP check dated 2026-10-03 recorded status 200 from IP 34.117.33.233, assigned to Google Cloud in the US. Google Safe Browsing, checked 2026-09-30, flagged the domain with the threat category social engineering. VirusTotal, checked 2026-09-29, reported 19 detections across 91 scanners. The SSL scan dated 2026-09-18 recorded the issuer as Google Trust Services / WR3. PhishDestroy's internal listing records the domain, and the first observation is dated 2026-09-17, when the PageSpeed performance score was 98.
Interpretation
The named records describe a domain that returned a successful HTTP response on the recorded date while appearing in a Safe Browsing flag and a publisher-owned catalogue. These are separate source observations with different dates, so they should be read as distinct records rather than a single combined measurement. The chronology shows the earliest recorded observation preceding the Safe Browsing flag and VirusTotal check, but the dates alone do not establish a trend or change in behavior.
Recommended Actions
Preserve the HTTP check, Safe Browsing flag, VirusTotal result, and PhishDestroy listing for security-server-landing-page--obipsalms.replit.app as separate records. Compare the Safe Browsing flag against the VirusTotal result in separate sentences when reviewing the domain, since each source applies its own criteria. Retain the PageSpeed and SSL scan records alongside these for a fuller picture of the recorded observations.
For the registrable domain replit.app behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Certificate fingerprint4a74494d584027de8f1b50d93d1683733368fbaea4298191709beefd53e0b0aeCertificate names · 1 SANs
replit.app
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-13 22:07:37 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:07:37 UTClast content: 2026-10-03 10:28:21 UTC
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.
技术 · 5 identified
Google Cloud
IaaS
Google Cloud is a suite of cloud computing services.
Google PageSpeed Insights — mobile performance audit of security-server-landing-page--obipsalms.replit.app· checked Sep 17, 2026
98
Good
Performance
FCP
1.85s
First Contentful Paint
LCP
1.95s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.85s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-10-09 01:47:39 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-10-05 22:20:13 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-18 19:25:24 UTC
VirusTotal scanner detections updated from 17 to 11. Resolved alerts: CyRadar, Gridinsoft, Lionic, Sophos, URLQuery, VIPRE.
VirusTotal Detections Update2026-09-17 16:08:06 UTC
VirusTotal scanner detections updated from 3 to 17. Added scanner alerts: BitDefender, ESET, Emsisoft, Fortinet, G-Data, Google Safe Browsing, Kaspersky, LevelBlue, Lionic, Netcraft, Sophos, URLQuery, VIPRE, Webroot.
VirusTotal Detections Update2026-09-17 14:34:54 UTC
VirusTotal scanner detections updated from 2 to 3. Added scanner alerts: Gridinsoft.
Status Check2026-09-17 13:33:11 UTC
Telemetry event observed.
Threat First Observed2026-09-17 13:32:39 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 34.117.33.233.
威胁响应 Pipeline
发现
Analysis
Monitoring
17 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
