jomang27.github.io returned an HTTP 404 status on 2026-10-07, confirming that the requested page was not found at that time. Google Safe Browsing flagged this domain for social engineering on 2026-09-15, which is a significant security observation.
Recorded Evidence
On 2026-09-15, Google Safe Browsing identified jomang27.github.io for social engineering. VirusTotal on the same date reported 13 detections out of 89 scanners. The domain appeared in the PhishDestroy internal listing. An HTTP check on 2026-10-07 returned a 404 status, and a PageSpeed performance score of 100 was recorded on 2026-09-11.
Interpretation
These records from Google Safe Browsing, VirusTotal, and the PhishDestroy internal listing highlight that several monitoring sources have noted jomang27.github.io. The HTTP 404 status only describes the response for a specific request on the checked date and does not provide information about other possible content.
Recommended Actions
Review the Google Safe Browsing and VirusTotal records for jomang27.github.io for reference in future evaluations. Preserve the HTTP response and PhishDestroy internal listing records for comparison with later observations. Use the PageSpeed performance score to supplement technical reviews of the domain.
Detection-evasion analysis
Cloaking suspected: scanner and visitor titles differ
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.
Google Safe BrowsingFlaggedSocial engineeringchecked Sep 15, 2026
IP ContextGitHub Pages shared edgeorigin IP hiddenEdge-IP reputation is not attributed to this domain.
Platform providerMarkMonitor(US)
HTTP Status404 Not Found
Technical detailsProvenance & timestamps
First DetectedSep 11, 2026
Submitted URLhttp://jomang27.github.io/Facebook
Page Title
Facebook
Impersonates
Facebook
TLS Certificate
Hostname coverage not recorded·
Issued by YR1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
185.199.109.153
Observed location
US
Server header
GitHub.com
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
TLS certificate
Issuer
YR1
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 outcomeInactivereason: Http No Content70% confidence
Attributionsource: Current Http Probe
Evidence layersAvailability: Root path has no contentContent: Absent At RootDNS: StaleRegistration: Unknown
Latest HTTP observationInactiveHttp No Content70%2026-10-13 01:15:48 UTC
RDAP registrationUnknown
Observed timelinecurrent episode first observed: 2026-10-09 01:25:30 UTCfirst terminal observation: 2026-10-01 01:39:05 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.
Fastly is a cloud computing services provider. Fastly's cloud platform provides a content delivery network, Internet security services, load balancing, and video & streaming services.
Last analyzed Previous stored snapshot: 12 detections
alphaMountain.ai
BitDefender
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
G-Data
Google Safe Browsing
Gridinsoft
MalwareURL
Netcraft
URLQuery
Webroot
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of jomang27.github.io· checked Sep 11, 2026
100
Good
Performance
FCP
0.79s
First Contentful Paint
LCP
0.79s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.79s
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.
VirusTotal Detections Update2026-09-15 17:53:14 UTC
VirusTotal scanner detections updated from 12 to 13. Added scanner alerts: MalwareURL.
VirusTotal Detections Update2026-09-14 22:19:00 UTC
VirusTotal scanner detections updated from 10 to 12. Added scanner alerts: BitDefender, URLQuery.
Domain Status Transition2026-09-11 04:15:12 UTC
Domain state transitioned from alive to dead.
Status Check2026-09-11 03:29:32 UTC
Telemetry event observed.
Threat First Observed2026-09-11 03:28:55 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 185.199.109.153.
Threat Response Pipeline
Discovery
Analysis
Monitoring
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
jomang27.github.io 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 11, 2026
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.
3 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 · jomang27.github.io
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)
