ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@godaddy.com.
The latest stored availability evidence still shows the domain reachable; 14 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
On 2026-10-02, an HTTP status of 200 was recorded for x7tq54amsloginx7tq92.portal-login-access.net. returned an HTTP status of 200 during that check. Google Safe Browsing flagged the full domain x7tq54amsloginx7tq92.portal-login-access.net for social engineering on the same date.
Recorded Evidence
PhishFeed listed the domain on the external blocklist checked 2026-10-02. VirusTotal recorded 22 detections across 91 scanners on 2026-09-26. Google Safe Browsing flagged social engineering on 2026-10-02. The domain was first observed on 2026-09-26, the same date as the PageSpeed performance score of 100. The SSL certificate, issued by Let's Encrypt / YR2, was scanned on 2026-09-27. The IP 172.174.53.244 is in the US under Microsoft Azure Cloud (eastus).
Interpretation
The PhishFeed listing and the Google Safe Browsing social engineering flag are named source observations recorded on 2026-10-02. VirusTotal detections and the first observation share the 2026-09-26 date, while the SSL scan on 2026-09-27 and the HTTP check on 2026-10-02 fall on later dates. These dated records allow comparison across sources without establishing a verdict.
Recommended Actions
For x7tq54amsloginx7tq92.portal-login-access.net, preserve the PhishFeed listing, the Google Safe Browsing social engineering flag, and the VirusTotal detection record as separate source artifacts. Compare the HTTP response record against the blocklist and Safe Browsing records to see whether the named sources agree. Retain the PageSpeed and SSL scan records for chronological comparison with the first observation. Review the domain against the recorded source observations before deciding on any access or filtering step.
Certificate hostname mismatch·
発行者 Let's Encrypt / YR2· stored validity ends in 63 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
172.174.53.244
Network ASN
AS8075
Organization
Microsoft Azure Cloud (eastus)
Observed location
Boydton, US
Server header
Microsoft-IIS/10.0
ネームサーバー 4
ns-1083.awsdns-07.org
ns-1832.awsdns-37.co.uk
ns-214.awsdns-26.com
ns-580.awsdns-08.net
Location describes the IP network.
TLS証明書
Issuer
Let's Encrypt / YR2
Valid from
2026-09-15 04:46:28
Valid until
2026-12-14 04:46:27
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-26 22:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint31c80518a590590d45fc35ed29fcfb3964b5190e832e145a0018b58449e4e7f1Certificate names · 1 SANs
portal-login-access.net
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-11 01:45:59 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 01:45:59 UTClast content: 2026-10-11 01:45:59 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.
使用技術 · 3 identified
W
Windows Server
Operating systems
Windows Server is a brand name for a group of server operating systems.
Google PageSpeed Insights — mobile performance audit of x7tq54amsloginx7tq92.portal-login-access.net· checked Sep 26, 2026
100
Good
Performance
FCP
0.78s
First Contentful Paint
LCP
0.78s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.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.
VirusTotal Detections Update2026-09-28 17:01:22 UTC
VirusTotal scanner detections updated from 21 to 22. Added scanner alerts: CyRadar.
VirusTotal Detections Update2026-09-27 04:33:05 UTC
VirusTotal scanner detections updated from 20 to 21. Added scanner alerts: LevelBlue.
VirusTotal Detections Update2026-09-26 23:52:26 UTC
VirusTotal scanner detections updated from 20 to 20. Added scanner alerts: Google Safe Browsing, Seclookup. Resolved alerts: LevelBlue, OpenPhish.
Status Check2026-09-26 19:43:07 UTC
Telemetry event observed.
Threat First Observed2026-09-26 19:11:54 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 172.174.53.244.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
15 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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
