libertyuniversityportal.com returned HTTP status 502 in an HTTP check dated 2026-10-01, a recorded server response for that request. The domain was first observed on 2026-09-12 and registered on 2026-09-03 with NameCheap, Inc., according to the recorded registration data.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 502 for libertyuniversityportal.com. VirusTotal, checked on 2026-09-20, reported 2 detections across 89 scanners. OTX, checked on 2026-09-20, listed 2 pulses. The domain appears in the PhishDestroy internal listing, and the registrar is NameCheap, Inc., with registration on 2026-09-03. First observation was 2026-09-12.
Interpretation
The HTTP 502 record describes one response at a single check, not the domain's full content or present availability. The VirusTotal and OTX figures reflect separate source measurements on their own check dates, so they should be read as distinct observations rather than a combined score. The registration and first-observation dates precede the HTTP check, which places the recorded response later in the available timeline.
Recommended Actions
Preserve the HTTP check record for libertyuniversityportal.com and the VirusTotal and OTX entries as separate source documents. Compare the HTTP response record against the PhishDestroy internal listing in a later review. Recheck the domain's HTTP status and re-query VirusTotal and OTX to update the recorded observations.
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='libertyuniversityportal.com', port=80): Max retries exceeded with url: / (Caused by NewCon
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 12, 2026
Network & certificates
Stored technical evidence
Network & DNS
Nameservers 1
johnny.ns.cloudflare.com
Location describes the IP network.
Latest Classified Outcome 2026-10-13 08:22:38 UTC
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:05 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-12 05:28:09 UTCcurrent episode first observed: 2026-09-30 16:26:51 UTCobserved RIP window: 2026-09-12 05:28:09 UTC → 2026-09-30 16:26:51 UTC · 442.98hmidpoint estimate ≈ 2026-09-21 10:57:30 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.
7 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
libertyuniversityportal.com detected and queued for full analysis
Sep 12, 2026
Cloudflare Radar Report
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 19, 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.
2 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 · libertyuniversityportal.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.
Same registrar: NameCheap6
Registered through the same registrar. A registrar serves millions of unrelated customers, so this groups reports rather than proving a link.
(US)
