Skip to security report
Domain security and threat intelligence
pipelife.services favicon

pipelife.services

In short

pipelife.services is a credential phishing page detected by PhishDestroy on 2026-07-27. Risk: critical (81/100). Registrar: IONOS SE. Status: Last known active. Hosting: IONOS SE. PhishDestroy sent 1 abuse report. VirusTotal: 4/89 engines flag it. Do not enter credentials or connect a wallet.

“Home - Pipelife Services”

Registrar
IONOS SE
Resolved IP
217.160.0.54
Registered
Jun 21, 2022
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 4/89 Scam type: Credential Phishing
OTX: 3 refs Jul 27, 2026 1 Report Sent
API
This domain has been flagged as malicious
Security engines reporting a detection: 4. Exercise extreme caution — do not enter credentials or personal information.
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@ionos.com. The latest stored availability evidence still shows the domain reachable; 2 months 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.

Elapsed since first report
2 months
Reports sent
1
Latest case ID
PD-20260727-57F409
Current status
HTTP 301 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Source evidenceVirusTotal 4 / 89 · OTX 3 references 8 sources

VirusTotal

4 / 89 engine detections

Open report

URLQuery

checked — no detections recorded

Open report

OTX

3 community references

Open report

Gridinsoft

62/100

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

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

Analysis

Critical
VirusTotal
4 / 89
OTX
3 community refs
Page captures
4

PhishDestroy threat report

Analysis of pipelife.services indicates an active credential harvesting phishing domain with high-risk infrastructure. The domain was registered on June 21, 2022, through IONOS SE and remains operational as of July 27, 2026. It resolves to the IP address 217.160.0.54, hosted under a provider commonly associated with both legitimate and malicious activity. Nameserver records (ns1047.ui-dns.de, ns1048.ui-dns.org, ns1058.ui-dns.biz, ns1101.ui-dns.com) suggest use of a managed DNS service, which may facilitate rapid domain changes or evasion tactics.

Detection data is limited but notable: one of 91 security vendors on VirusTotal has flagged the domain, and it appears on a single security blocklist (PhishDestroy). No additional context regarding the specific brand targeted or phishing kit in use is available at this time. The absence of broader detection does not confirm safety, as phishing domains often evade initial scans through cloaking or delayed activation. Defenders should treat this domain as high-risk based on its active status, hosting on a known phishing-associated IP, and confirmed blocklist presence.

Immediate mitigation steps include blocking the domain and IP at perimeter security controls, monitoring for internal connections, and investigating any user reports of interaction with the site. Further analysis of HTTP headers, SSL certificates, or captured page content may clarify the exact phishing methodology or targeted brand. Given the domain's age and continued operation, it is likely part of a persistent campaign rather than a short-lived scam.

Collected source details

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

URLScan · 2026-07-27T05:17:08Z

Observed: · Retrieved:

Uuid
019fa201-4ae3-752f-bad0-715d0e103276
Final url
https://www.pipelife.services/
Status
200
Redirected
parent-domain
Redirects
[
    {
        "to": "https://www.pipelife.services/",
        "from": "https://pipelife.services/",
        "status": 301
    }
]
Ip
2001:8d8:100f:f000::2ea
Contacted domains
[
    "fonts.gstatic.com",
    "in-automate.brevo.com",
    "fonts.googleapis.com",
    "sibautomation.com",
    "cdn.brevo.com",
    "pipelife.services"
]
Contacted IP addresses
[
    "2606:4700:4401::6812:2528",
    "2a00:1450:4001:c25::5f",
    "2a06:98c1:3200::90:80",
    "192.178.183.94",
    "2a06:98c1:3200::90:81",
    "2001:8d8:100f:f000::2ea"
]
Asns
[
    "13335",
    "15169",
    "8560"
]
Countries
[
    "DE",
    "US"
]
Linked domains
[
    "www.facebook.com",
    "www.xing.com",
    "www.youtube.com",
    "twitter.com",
    "www.pipelife.de"
]
Social
[
    "https://www.facebook.com/PipelifeDeutschlandGmbH",
    "https://www.youtube.com/playlist",
    "https://twitter.com/pipelife"
]
Document hash
8e7c78d2be83a06254dd7da6a189ce0885f6c669d78b66d0bf8bd2f424043767
Script hashes
[
    "6dbc3e667cfad81b4cb74a82dd4d808eecf27713f50a1791c385bb29fce753d4",
    "c6595b94b16bd9d25dd8c3bde2627812465287236eed2bea6c288cf92ec37909",
    "cb6f2d32c49d1c2b25e9ffc9aaafa3f83075346c01bcd4ae6eb187392a4292cf",
    "5274f11e6fb32ae0cf2dfb9f8043272865c397a7c4223b4cfa7d50ea52fbde89",
    "8d8b5d43a745a2fc2f1aff8f93a3c98f83ac8d3e0cfb731a8403d8e95ea5fc3b",
    "62ddafe937aade73e04ff280126ae7f96dfdfbc7986f7510e52e3b4875846f69",
    "c4596b16b126326b0d8fc2fb8bf91389ad3dc4671a269187913c19a8f2ad1094",
    "c5f3b2f654d2d8210a481c0164f0a53430cd09b77c34374fe23c9a03f5ad00fb",
    "33a41aa366d15cc6db2395d774147d6e1de6d5669f34f66104f964073dd0e469",
    "5d9ce604b32276fc218d30221fa3b528285a3155a0b32bb55c12215d3091d662"
]
Globals
[
    "WebFont",
    "realCookieBanner",
    "consentApi",
    "jQuery",
    "sibErrMsg",
    "ajax_sib_front_object",
    "sibVerifyCallback",
    "errorCallbackForTurnstileErrors",
    "Brevo",
    "setREVStartSize",
    "doc",
    "RS_MODULES",
    "fusionNavIsCollapsed",
    "fusionRunNavIsCollapsed",
    "avadaGetScrollBarWidth",
    "wpforms_user_journey",
    "WPFormsUserJourney",
    "gsapVersions",
    "tpGS",
    "punchgs",
    "RSANYID",
    "RSANYID_sliderID",
    "cssua",
    "fusionAnimationsVars",
    "fusionSetAnimationData",
    "fusionJSVars",
    "fusion",
    "fusionLightboxVideoVars",
    "_fusionRefreshScroll",
    "_fusionParallaxAll",
    "_fusionRefreshWindow",
    "fusionVideoGeneralVars",
    "playVideoAndPauseOthers",
    "fusionVideoBgVars",
    "$youtubeBGVideos",
    "_fbRowGetAllElementsWithAttribute",
    "_fbRowOnPlayerReady",
    "_fbRowOnPlayerStateChange",
    "resizeVideo",
    "vimeoReady"
]
Cookies
[
    "_wpfuj",
    "sib_cuid"
]
Storage keys
[
    "modernizr",
    "wpEmojiSettingsSupports"
]
Tls
{
    "san": [
        "*.pipelife.services",
        "pipelife.services"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "Sectigo Public Server Authentication CA DV R36",
    "subject": "*.pipelife.services",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-13T23:59:59Z",
    "valid_from": "2026-07-03T00:00:00Z"
}
Domain age days
1435
Apex age days
1495
Tls age days
24
Tls valid days
194
Requests
42
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": -40,
        "malicious": false
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Apache",
    "content-type": "text/html"
}
Cloudflare Radar · 2026-07-27T05:01:51Z

Observed: · Retrieved:

Uuid
d97d2433-3300-4a18-ab9a-4589ed4a8e30
Final url
https://www.pipelife.services/
Status
200
Redirected
subdomain
History
[
    {
        "url": "https://pipelife.services/",
        "status": 301
    },
    {
        "url": "https://www.pipelife.services/",
        "status": 200
    }
]
DOM structure hash
ebbca17559a6cdc20c720a5b99eea89bd8d3fa8f35fa0b7c513e42a91697fe0f
Document hash
8e7c78d2be83a06254dd7da6a189ce0885f6c669d78b66d0bf8bd2f424043767
Domain risks
[
    "Login Screens",
    "Miscellaneous"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "pipelife.services",
        "type": "A",
        "value": "217.160.0.54"
    },
    {
        "name": "pipelife.services",
        "type": "AAAA",
        "value": "2001:8d8:100f:f000::2ea"
    },
    {
        "name": "www.pipelife.services",
        "type": "A",
        "value": "217.160.0.54"
    },
    {
        "name": "www.pipelife.services",
        "type": "AAAA",
        "value": "2001:8d8:100f:f000::2ea"
    }
]
Dnssec valid
false
Ip
217.160.0.54
Registration record
{
    "registrar": "IONOS SE",
    "created": "2022-06-21T11:09:00Z",
    "updated": "2026-06-21T11:09:20Z",
    "expires": "2027-06-21T11:09:00Z",
    "nameservers": [
        "ns1047.ui-dns.de",
        "ns1048.ui-dns.org",
        "ns1101.ui-dns.com",
        "ns1058.ui-dns.biz"
    ]
}

Questions about pipelife.services

Is pipelife.services legit?

No. PhishDestroy classifies pipelife.services as a credential phishing page (risk: critical, 81/100); it was first detected on 2026-07-27. VirusTotal: 4/89 engines flag it. Treat the site as unsafe.

Is pipelife.services safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on pipelife.services. 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 pipelife.services?

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 · 4 captures

Observed page title
Home - Pipelife Services
Automated brand references
Facebook YouTube
TLS Certificate
Issued by Sectigo Limited · stored validity ends in 170 days

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Sep 25, 2026
OTX tags 2026-07activeall-domainsblocklistcontentcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar IONOS SE (Unknown)
RegistrationCreated Jun 21, 2022 — Expires Jun 21, 2027
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First DetectedJul 27, 2026
DOM Analysisanalyzed Oct 9, 2026score 81/1002 brand signals
Submitted URLhttps://pipelife.services/
Favicon Hash
Case ID
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, 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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
217.160.0.54
Network ASN
AS8560
Organization
Ionos Inf
Observed location
Essen, DE
Server header
Apache

Nameservers 4

  • ns1047.ui-dns.de
  • ns1048.ui-dns.org
  • ns1058.ui-dns.biz
  • ns1101.ui-dns.com

Mail routing 2 MX records

  • mx01.ionos.depriority 10
  • mx00.ionos.depriority 10

Location describes the IP network.

TLS certificate

Issuer
Sectigo Limited
Valid from
2026-07-03 00:00:00
Valid until
2027-01-13 23:59:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-10 13:03:30 UTC
Collection source
PhishDestroy collector
Certificate fingerprintd966f9c24b3d6b162a5d6fa363f4743df53b8eb9ad668e7c567f5135bc88b4bd
Certificate names · 2 SANs
  • *.pipelife.services
  • pipelife.services

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

Latest Classified Outcome 2026-10-22 10:32:57 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-22 10:32:57 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:32:57 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.
Technologies · 9 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

4 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
CRDF
Gridinsoft
SOCRadar

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of pipelife.services · checked Jul 27, 2026

61
Needs Work
Performance
FCP
5.73s
First Contentful Paint
LCP
8.01s
Largest Contentful Paint
CLS
0.011
Cumulative Layout Shift
TBT
3ms
Total Blocking Time
SI
5.73s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history24

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Unavailable→Reachable

  4. Availability monitor · Recorded state

    Reachable→Unavailable

  5. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

Earlier observations 19
  1. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Unavailable→Reachable

  6. Availability monitor · Recorded state

    Reachable→Unavailable

  7. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  8. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  9. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  10. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  11. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  12. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  13. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  14. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  15. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  16. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  17. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  18. Availability monitor · Recorded state

    redirected

    http_redirect

  19. Availability monitor · First collection record

    Reachable

Recorded activity

6 entries
  1. AlienVault OTX

    3 community references

    View source
  2. VirusTotal

    4/89 engine detections

    View source
  3. Abuse report sent

    PD-20260727-57F409

    abuse@ionos.com
  4. URLScan

    Page captured

    View source
  5. Google Safe Browsing

    No threat flag

    View source
  6. Added to PhishDestroy

    pipelife.services

    View source

Community intelligence

1 community report

CategoryPHISHING

The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-07-21T06:52:13.312Z.

Check for cloaking

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

pipelife.services

Evidence & External Reports

Third-Party Detection — ChainAbuse
1 report filed for pipelife.services · category: Phishing · source checked
Flagged by PhishFort Detection System on Jul 21, 2026 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260727-57F409 Recipient: abuse@ionos.com
PDF notice generated Notice text archived (241 chars)
Abuse notice text as sent to the provider
Registrar: IONOS Registrar UK (United Kingdom)
Policy Violations: “Illegal activity including phishing, malware and fraud prohibited; registrar may suspend domains without notice.”
Applicable Laws: UK Computer Misuse Act 1990; Fraud Act 2006
Deep Analysis
Help & reporting

Were You Affected by This Site?

8 evidence signal groups linked 1 stored notification records Last known active
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.

Official reporting routes

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 →

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 pipelife.services)
  • 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

Stay Informed, Stay Safe

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

Live Threat Feed Appeal This Listing
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.

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/pipelife.services"
  title="PhishDestroy threat report for pipelife.services"
  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>