Skip to security report
Analytics Dashboard
Domain security and threat intelligence
connectnext.net favicon

connectnext.net

In short

connectnext.net is a phishing page detected by PhishDestroy on 2026-10-25.

“connectnext.net”

Review the evidence
Registrar
PDR
Resolved IP
134.122.44.253
Registered
May 12, 2020
PhishDestroy assessment Critical
First observed Oct 25, 2026 03:00 UTC · PhishDestroy
Risk signals
VirusTotal detections: 17/92
VirusTotal
17 / 92
engine detections
OTX
3
community references
Cloudflare Radar
malicious
source verdict
Page captures
6
open gallery
Domain age
2356 days
Reports sent
—
No sent record
OTX: 3 refs Oct 25, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 17. Exercise extreme caution — do not enter credentials or personal information.

Analysis

Domain summary

connectnext.net is a phishing page detected by PhishDestroy on 2026-10-25. Risk: critical (95/100). Registrar: PDR. Hosting: DigitalOcean, LLC. VirusTotal: 17/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
17 / 92
OTX
3 community refs
Page captures
6
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy added connectnext.net to its internal blocklist on 2026-10-25. The site returned HTTP 200 with no recorded page title at the time of capture. The listing reflects an automated risk assessment rather than observed malicious activity. A page fetch on 2026-10-25 recorded an HTTP 200 response, indicating the site was reachable at that time.

How the scam works

Vendor detections label the domain as phishing, a category that typically involves presenting a counterfeit login or request page to capture user credentials. No concrete phishing page was captured for this domain, so the precise technique cannot be confirmed. The assessment therefore reflects a potential phishing risk without evidence of a specific exploit.

Evidence

VirusTotal analysis on 2026-10-24 reported 14 malicious and 3 suspicious detections out of 92 engines, totaling 17 flags. Vendors such as BitDefender, ESET, Fortinet and others contributed phishing or malicious labels. Google Safe Browsing checked on 2026-10-25 did not flag the domain. PhishDestroy’s internal blocklist marked it as suspicious on 2026-10-25. OTX listed three pulses referencing the domain on the same day. urlscan captured the site on 2026-10-14, returned an overall clean verdict but its engine scoring marked it malicious with a score of 73. Cloudflare Radar on 2026-10-25 classified the domain as malicious under the malware category.

Infrastructure

The domain was registered on 2020-05-12 through PDR Ltd. d/b/a PublicDomainRegistry.com. The recorded A record pointed to IP 134.122.44.253, which was associated with DigitalOcean, LLC in Canada. Nameservers are ns1.node3389.myfcloud.com, ns2.node3389.myfcloud.com, ns3.mysecurecloudhost.com and ns4.mysecurecloudhost.com. TLS was provided by Let’s Encrypt for the SAN cryotomasyon.com, valid from 2026-10-13 to 2027-01-11.

What to do

Visitors should avoid entering any credentials or personal data on the site and should change passwords if they suspect they may have been entered. Organizations should block connectnext.net at the DNS or proxy level, monitor outbound connections to 134.122.44.253, and review logs for any access attempts. Security teams can add the domain to threat intelligence feeds and continue to monitor VirusTotal and other sources for updates.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-25T03:03:47Z)URLScan screenshot (2026-10-14T01:46:03Z)URLScan capture reportURLScan screenshot (2026-10-25T03:01:14Z)URLScan capture reportURLScan screenshot (2026-10-25T03:04:18Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 17 / 92 · OTX 3 references 5 sources

VirusTotal

17 / 92 engine detections

Open report
VirusTotal · 2026-10-24T04:13:45Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 43,
    "malicious": 14,
    "suspicious": 3,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Created
2020-05-12T00:00:00Z
First seen
2026-10-08T16:03:53Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.mysecurecloudhost.com"
    },
    {
        "ttl": 14400,
        "type": "A",
        "value": "134.122.44.253"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns4.mysecurecloudhost.com"
    },
    {
        "ttl": 21600,
        "type": "SOA",
        "rname": "servers.mysecurecloudhost.com",
        "value": "ns1.mysecurecloudhost.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns3.mysecurecloudhost.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.mysecurecloudhost.com"
    }
]
Dns at
2026-10-24T04:19:08Z
Jarm
2ad2ad0002ad2ad00042d42d0000005d86ccb1a0567e012264097a0315d7a7
Certificate
{
    "san": [
        "cryotomasyon.com"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "5424557f9192c135a29dd47eefbff66fea2",
    "sha256": "53d6c656e9421ef51574321d5dbb79893e9eca8b57e8cb8c593f153783ea7336",
    "subject": "cryotomasyon.com",
    "valid_to": "2027-01-20T07:03:58Z",
    "valid_from": "2026-10-22T07:03:59Z"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "last changed": "2026-10-04T05:05:37Z",
        "registration": "2020-05-12T17:52:45Z",
        "registrar expiration": "2027-05-12T17:52:45Z",
        "last update of RDAP database": "2026-10-24T04:19:12Z"
    },
    "registrar": "PDR Ltd. d/b/a PublicDomainRegistry.com",
    "registrar_iana_id": "303"
}

Cloudflare Radar

Malicious

Not recorded
Open report
Cloudflare Radar · 2026-10-25T03:03:47Z

Observed: · Retrieved:

Uuid
fe0f05d1-9d83-4e77-a0a1-ae8775962588
Final url
https://connectnext.net/
History
[
    {
        "url": "https://connectnext.net/",
        "status": 0
    }
]
DOM structure hash
94bfc7c24186e5b245b5675859fb84b248547086370961e5637590177432b219
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "connectnext.net",
        "type": "A",
        "value": "134.122.44.253"
    }
]
Dnssec valid
false
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "PDR Ltd. d/b/a PublicDomainRegistry.com",
    "created": "2020-05-12T17:52:45Z",
    "updated": "2026-10-04T05:05:36Z",
    "expires": "2027-05-12T17:52:45Z",
    "nameservers": [
        "ns1.node3389.myfcloud.com",
        "ns2.node3389.myfcloud.com",
        "ns3.mysecurecloudhost.com",
        "ns4.mysecurecloudhost.com"
    ]
}

OTX

3 community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Not recorded
Open report
URLScan · 2026-10-14T10:20:56Z

Observed: · Retrieved:

Uuid
01a139ed-c9f6-7748-b49b-3780b747ac4b
Final url
https://connectnext.net/
Status
200
Redirected
https-only
Ip
134.122.44.253
Contacted IP addresses
[
    "134.122.44.253"
]
Asns
[
    "14061"
]
Countries
[
    "CA"
]
Document hash
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Tls
{
    "san": [
        "connectnext.net"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "connectnext.net",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-11T17:50:08Z",
    "valid_from": "2026-10-13T17:50:09Z"
}
Domain age days
1338
Apex age days
1338
Tls age days
0
Tls valid days
89
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 73,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checks · 2026-10-25T03:04:40Z
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "connectnext.net"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2017-09-14T07:51:13Z",
    "first": "2007-11-02T07:57:59Z",
    "changes": 2,
    "days_archived": 16,
    "scans_per_day": 0,
    "avg_page_bytes": 1586
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": false,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "99.83.147.209",
            "host": "ns4.mysecurecloudhost.com"
        },
        {
            "ip": "13.248.158.180",
            "host": "ns1.mysecurecloudhost.com"
        },
        {
            "ip": "75.2.118.134",
            "host": "ns2.mysecurecloudhost.com"
        },
        {
            "ip": "76.223.26.245",
            "host": "ns3.mysecurecloudhost.com"
        }
    ],
    "zone": "connectnext.net"
}
Location
{
    "ip": "134.122.44.253",
    "asn": "14061",
    "org": "DigitalOcean, LLC",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YR1",
    "subject": "cryotomasyon.com"
}
DNS records
{
    "A": [
        "134.122.44.253"
    ],
    "NS": [
        "ns2.mysecurecloudhost.com",
        "ns1.mysecurecloudhost.com",
        "ns3.mysecurecloudhost.com",
        "ns4.mysecurecloudhost.com"
    ],
    "SOA": "{\"nsname\": \"ns1.mysecurecloudhost.com\", \"hostmaster\": \"servers.mysecurecloudhost.com\", \"serial\": 2026101206, \"refresh\": 3600, \"retry\": 1800, \"expire\": 1209600, \"minttl\": 86400}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "134.122.44.253",
    "family": 4
}
Registration record
{
    "registrar": "PDR Ltd. d/b/a PublicDomainRegistry.com",
    "created": "2020-05-12T17:52:45Z",
    "updated": "2026-10-04T05:05:36Z",
    "expires": "2027-05-12T17:52:45Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.node3389.myfcloud.com",
        "ns2.node3389.myfcloud.com",
        "ns3.mysecurecloudhost.com",
        "ns4.mysecurecloudhost.com"
    ]
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware Security threats Malware
View full Cloudflare Radar report

Questions about connectnext.net

Is connectnext.net legit?

No. PhishDestroy classifies connectnext.net as a phishing page (risk: critical, 95/100); it was first detected on 2026-10-25. VirusTotal: 17/92 engines flag it. Treat the site as unsafe.

Is connectnext.net safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on connectnext.net. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used connectnext.net?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 6 captures

Primary capture 1 / 6
SourcePrimary capture
Recorded
StateStored capture
HTTP status200
Final URLhttps://connectnext.net/
Position1 / 6
Open capture Wayback Download
All capture links and hashes (6)

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 25, 2026
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar PDR IN(IN)
Abuse contact["a9a3dba978ab7f47s@gmail.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for connectnext.net →
RegistrationCreated May 12, 2020 — Expires May 12, 2027
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
Submitted URLhttp://connectnext.net/
Observed page title
connectnext.net
TLS Certificate
Issued by Let's Encrypt / YR1 · stored validity ends in 86 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
134.122.44.253
Network ASN
AS14061
Organization
DigitalOcean, LLC
Observed location
Toronto, CA

Nameservers 4

  • ns1.node3389.myfcloud.com
  • ns2.node3389.myfcloud.com
  • ns3.mysecurecloudhost.com
  • ns4.mysecurecloudhost.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR1
Valid from
2026-10-22 07:03:59
Valid until
2027-01-20 07:03:58
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint53d6c656e9421ef51574321d5dbb79893e9eca8b57e8cb8c593f153783ea7336
Certificate names · 1 SAN
  • cryotomasyon.com

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 134.122.44.253rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

17 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 17 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of connectnext.net · checked Oct 25, 2026

100
Good
Performance
FCP
0.78 s
First Contentful Paint
LCP
0.78 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.22 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://connectnext.net/
Redirecting...
Response
HTTP 200
HTML body
533 B
Compressed
299 B
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx/1.18.0 (Ubuntu)
Content-Type: text/html
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 8
Accept-Ranges
bytes
Connection
keep-alive
Content-Length
533
Content-Type
text/html
Date
Sun, 25 Oct 2026 03:01:14 GMT
Etag
"6ad927bb-215"
Last-Modified
Wed, 21 Oct 2026 20:59:39 GMT
Server
nginx/1.18.0 (Ubuntu)

Values retained by the collector; long values may be shortened during collection.

Archived
All retained availability observations1

Source: availability monitor. This journal includes earlier observations and repeated states with distinct dates or evidence. Identical records appear once; an unknown state is not proof that the site is offline.

  1. unknown
    Cause
    stale_current_evidence
    Monitor confidence
    0
    Original source timestamp
    2026-10-25 04:05:11.043361
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b

Recorded activity

3 entries
  1. AlienVault OTX

    3 community references

    View source
  2. VirusTotal

    17/92 engine detections

    View source
  3. Added to PhishDestroy

    connectnext.net

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

connectnext.net

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 17 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch CF Radar Malicious OTX 3 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked Unverified
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.

Immediate steps Find reporting contacts

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including connectnext.net)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?
  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/connectnext.net"
  title="PhishDestroy threat report for connectnext.net"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>