Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 1/92 engines flagged. malicious: 1. suspicious: 0. Analysis time (as stored): 2026-10-28T07:12:07Z. Retrieved (as stored): 2026-10-29T03:09:46Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
chatgpt-girlfriend.com favicon

chatgpt-girlfriend.com

In short

The captured chatgpt-girlfriend.com landing page promotes an anime virtual girlfriend chat service, showing a hero heading, descriptive copy, and two calls to action: "Meet your girlfriend" and "See companions." A "Start chatting" button sits at the upper right, alongside usage statistics and an 18+ label.

“ChatGPT Girlfriend AI — Anime Virtual Girlfriend Chat, Free to Start”

Review the evidence
Registrar
United StatesPDR
Resolved IP
United Kingdom188.114.97.3CloudFLARENET-EU · CDN
First observed
Oct 28, 2026
PhishDestroy assessment Critical
72/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 1/92
VirusTotal
1 / 92
engine detections ·
OTX
4
community references
URLScan
Malicious
engine verdict · score 76
Page captures
5
open gallery
Reports sent
1
view timeline
OTX: 4 refs Oct 28, 2026 1 Report Sent CDN
X Telegram API
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-contact@publicdomainregistry.com. The latest stored availability evidence still shows the domain reachable; 8 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.

Elapsed since first report
8 days
Reports sent
1
Latest case ID
PD-A66CAFCDB97FEFEFA96A
Current status
HTTP 200 at latest stored check

Analysis

Domain summary

PhishDestroy first recorded chatgpt-girlfriend.com on 2026-10-28. Stored VirusTotal result: 1/92 engines flagged. malicious: 1. suspicious: 0. Analysis time (as stored): 2026-10-28T07:12:07Z. Retrieved (as stored): 2026-10-29T03:09:46Z. Risk: critical (72/100). Registrar: PDR. Status: Last known active. Hosting: CloudFLARENET-EU. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
1 / 92
Scam type (automated label)
Impersonation
Hosting
United Kingdom188.114.97.3CloudFLARENET-EU · CDN
Registrar
United StatesPDR
OTX
4 community refs
Page captures
5
Page captures Source results Registration record

Capture recorded with this analysis · Cloudflare Radar · 2026-10-28T21:17:46Z
SHA-256: 103675d940b00604a95f69113dea9968498f18228ac0bdbb7f403ace6884b3a4

PhishDestroy analysis, reviewed version

The captured chatgpt-girlfriend.com landing page promotes an anime virtual girlfriend chat service, showing a hero heading, descriptive copy, and two calls to action: "Meet your girlfriend" and "See companions." A "Start chatting" button sits at the upper right, alongside usage statistics and an 18+ label.

The stored VirusTotal result reports 1 of 92 engines flagged the domain, with CRDF labeling it "malicious." No other supplied vendor labels are available, so remaining detections are unknown. This scanner result alone does not establish impersonation or current behavior.

Source evidenceVirusTotal 1 / 92 · OTX 4 references 9 sources

VirusTotal

1 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
52
Malicious
1
Suspicious
0
Undetected
39

Vendor labels

CRDF
malicious

Reputation score

0

Tags

  • dga

Registrar

PDR Ltd. d/b/a PublicDomainRegistry.com

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3036::ac43:de6a
  • TTL, seconds
    21600
    Type
    NS
    Value
    leia.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.75.110
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3031::6815:4b6e
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.222.106
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    leia.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    ryan.ns.cloudflare.com

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.chatgpt-girlfriend.com
  • chatgpt-girlfriend.com
Issuer
Let's Encrypt / YE2
Serial
59e6b9ade73fce2f427e48f77e9146195e7
SHA-256
e7fed8710591d5acb20eab52b1d9c185cd6adf0afa563d69ce5cf552c3df2a71
Subject
chatgpt-girlfriend.com
Valid until
Valid from

Registration record

Registrar
PDR Ltd. d/b/a PublicDomainRegistry.com
Registrar IANA ID
303
Registrar URL
http://www.publicdomainregistry.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • leia.ns.cloudflare.com
  • ryan.ns.cloudflare.com
DNSSEC
Unsigned

Registry data (RDAP)

Status
  • client transfer prohibited
Registry events
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 52,
    "malicious": 1,
    "suspicious": 0,
    "undetected": 39
}
Vendor labels
{
    "CRDF": "malicious"
}
Reputation
0
Tags
[
    "dga"
]
Registrar
PDR Ltd. d/b/a PublicDomainRegistry.com
Created
2026-10-27T10:35:35Z
Expires
2027-10-27T10:35:35Z
Updated
2026-10-27T10:35:38Z
First seen
2026-10-27T10:43:47Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3036::ac43:de6a"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "leia.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.75.110"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3031::6815:4b6e"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.222.106"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "leia.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ryan.ns.cloudflare.com"
    }
]
Dns at
2026-10-28T07:12:55Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.chatgpt-girlfriend.com",
        "chatgpt-girlfriend.com"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "59e6b9ade73fce2f427e48f77e9146195e7",
    "sha256": "e7fed8710591d5acb20eab52b1d9c185cd6adf0afa563d69ce5cf552c3df2a71",
    "subject": "chatgpt-girlfriend.com",
    "valid_to": "2027-01-25T09:39:29Z",
    "valid_from": "2026-10-27T09:39:30Z"
}
Registration record
{
    "registrar": "PDR Ltd. d/b/a PublicDomainRegistry.com",
    "registrar_iana_id": "303",
    "registrar_url": "http://www.publicdomainregistry.com",
    "created": "2026-10-27T10:35:35Z",
    "updated": "2026-10-27T10:35:35Z",
    "expires": "2027-10-27T10:35:35Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "leia.ns.cloudflare.com",
        "ryan.ns.cloudflare.com"
    ],
    "dnssec": "Unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "last changed": "2026-10-27T10:35:38Z",
        "registration": "2026-10-27T10:35:35Z",
        "registrar expiration": "2027-10-27T10:35:35Z",
        "last update of RDAP database": "2026-10-27T10:43:42Z"
    }
}
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

source
VirusTotal
scope
unknown
result_state
observed
numerator
4
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","CRDF","Forcepoint ThreatSeeker","Gridinsoft"]
observed_at
null
checked_at
2026-11-02 04:01:24
fetched_at
2026-11-02 03:01:24
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Suspicious

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Report ID

f509387b-8adb-47f3-bc7a-02ff65b5aac7

Final URL

https://chatgpt-girlfriend.com/

HTTP response

200

Navigation history

  • URL
    https://chatgpt-girlfriend.com/
    Status
    200

DOM structure hash

542b6c8eb8e21419642830e7bee0692000765d70fb54fad57ddd5e54637ea656

Document hash

210861d497e41d5efdbcdd6b72b06466d1d1ca32d144c259cf9804bb19a19933

Domain risk categories

  • Newly Seen Domains
  • Security Risks
  • New Domains

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    chatgpt-girlfriend.com
    Type
    A
    Value
    104.21.75.110
  • Name
    chatgpt-girlfriend.com
    Type
    A
    Value
    172.67.222.106
  • Name
    chatgpt-girlfriend.com
    Type
    AAAA
    Value
    2606:4700:3036::ac43:de6a
  • Name
    chatgpt-girlfriend.com
    Type
    AAAA
    Value
    2606:4700:3031::6815:4b6e

DNSSEC valid

No

IP address

127.0.1.5

127.0.1.5 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record

Registrar
PDR Ltd. d/b/a PublicDomainRegistry.com
Registered
Updated
Expires
Nameservers
  • leia.ns.cloudflare.com
  • ryan.ns.cloudflare.com
Original source fields · JSON
Uuid
f509387b-8adb-47f3-bc7a-02ff65b5aac7
Final url
https://chatgpt-girlfriend.com/
Status
200
History
[
    {
        "url": "https://chatgpt-girlfriend.com/",
        "status": 200
    }
]
DOM structure hash
542b6c8eb8e21419642830e7bee0692000765d70fb54fad57ddd5e54637ea656
Document hash
210861d497e41d5efdbcdd6b72b06466d1d1ca32d144c259cf9804bb19a19933
Domain risks
[
    "Newly Seen Domains",
    "Security Risks",
    "New Domains"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "chatgpt-girlfriend.com",
        "type": "A",
        "value": "104.21.75.110"
    },
    {
        "name": "chatgpt-girlfriend.com",
        "type": "A",
        "value": "172.67.222.106"
    },
    {
        "name": "chatgpt-girlfriend.com",
        "type": "AAAA",
        "value": "2606:4700:3036::ac43:de6a"
    },
    {
        "name": "chatgpt-girlfriend.com",
        "type": "AAAA",
        "value": "2606:4700:3031::6815:4b6e"
    }
]
Dnssec valid
false
Ip
127.0.1.5

127.0.1.5 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record
{
    "registrar": "PDR Ltd. d/b/a PublicDomainRegistry.com",
    "created": "2026-10-27T10:35:35Z",
    "updated": "2026-10-27T10:35:35Z",
    "expires": "2027-10-27T10:35:35Z",
    "nameservers": [
        "leia.ns.cloudflare.com",
        "ryan.ns.cloudflare.com"
    ]
}

URLScan

Malicious · engine verdict · score 76

SHA-256 ecf6d829e12819658c9b84c1e7285e8ddbee25e00cb316dd2c36f7ab2205eb05

Open report
URLScanOriginal source recordObserved: 19 fields

Observed: · Retrieved:

Report ID

01a1843f-3261-712e-92d3-e47b1831148d

Final URL

https://chatgpt-girlfriend.com/

HTTP response

200

IP address

188.114.96.3

Contacted domains

  • fonts.gstatic.com
  • fonts.googleapis.com

Contacted IP addresses

  • 142.250.154.94
  • 2a00:1450:4001:c1f::5f
  • 188.114.96.3

Autonomous systems (ASN)

  • 15169
  • 13335

Server countries

  • US
  • DE

Document hash

fabd90374dbd446033a8bcfd0874d3020bac449f1c9dbe9adc44b1387d670f06

Script hashes

  • 775d26427dde5cc11472ecaf0f2c96172bd20777ac4863d7253b745ca99db2a3
  • 62508af17647e0662a426a2b1ec0816692212a1815c12e279d1aeec16a06345d

JavaScript globals

  • main

TLS session and certificate

Subject alternative names
  • *.chatgpt-girlfriend.com
  • chatgpt-girlfriend.com
Cipher
AES_128_GCM
Issuer
YE2
Subject
chatgpt-girlfriend.com
Protocol
QUIC
Valid until
Valid from

Domain age, days

1

Registered domain age, days

1

Certificate age, days

1

Certificate validity, days

89

Page requests

17

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
76
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
cloudflare
Content-type
text/html; charset=utf-8
Priority
u=0,i
Original source fields · JSON
Uuid
01a1843f-3261-712e-92d3-e47b1831148d
Final url
https://chatgpt-girlfriend.com/
Status
200
Ip
188.114.96.3
Contacted domains
[
    "fonts.gstatic.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "142.250.154.94",
    "2a00:1450:4001:c1f::5f",
    "188.114.96.3"
]
Asns
[
    "15169",
    "13335"
]
Countries
[
    "US",
    "DE"
]
Document hash
fabd90374dbd446033a8bcfd0874d3020bac449f1c9dbe9adc44b1387d670f06
Script hashes
[
    "775d26427dde5cc11472ecaf0f2c96172bd20777ac4863d7253b745ca99db2a3",
    "62508af17647e0662a426a2b1ec0816692212a1815c12e279d1aeec16a06345d"
]
Globals
[
    "main"
]
Tls
{
    "san": [
        "*.chatgpt-girlfriend.com",
        "chatgpt-girlfriend.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "chatgpt-girlfriend.com",
    "protocol": "QUIC",
    "valid_to": "2027-01-25T09:39:29Z",
    "valid_from": "2026-10-27T09:39:30Z"
}
Domain age days
1
Apex age days
1
Tls age days
1
Tls valid days
89
Requests
17
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 76,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8",
    "priority": "u=0,i"
}
Separate monitor record · 2026-10-29 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a1843f-3261-712e-92d3-e47b1831148d
score
0
malicious
false
result_at
2026-10-29T04:30:30Z
enriched_at
2026-10-29T09:15:42Z
source_timestamps
{"urlscan_result_at":"2026-10-29 05:30:30","urlscan_enriched_at":"2026-10-29 10:15:42"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

4 community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

10 / 100 · heuristic score · 1 brand reference · 1 classification

Open report
Separate monitor score · 10 / 100 · 2026-10-28T23:20:21Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
10
analyzed_at
2026-10-28T23:20:21Z
source_timestamp
2026-10-29 00:20:21
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
chatgpt-girlfriend.com anime AI companion chat landing page
ai_description
PhishDestroy records chatgpt-girlfriend.com, a landing page offering anime virtual girlfriend chat with companion selection and a free start.
ai_summary
The captured chatgpt-girlfriend.com landing page promotes an anime virtual girlfriend chat service, showing a hero heading, descriptive copy, and two calls to action: "Meet your girlfriend" and "See companions." A "Start chatting" button sits at the upper right, alongside usage statistics and an 18+ label. The stored VirusTotal result reports 1 of 92 engines flagged the domain, with CRDF labeling it "malicious." No other supplied vendor labels are available, so remaining detections are unknown. This scanner result alone does not establish impersonation or current behavior.
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-29 04:11:32
revision
317b82a5ed8e371e4cde3c9d458f61ab8d7a6263e4407bb724fe166367e00732
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

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 checksOriginal source recordRetrieved: 26 fields

Mail configuration

SPF lookups
0

CAA records

Domain
chatgpt-girlfriend.com

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
7451

Crawler rules

User agents
  • *
Present
Yes
Sitemap URLs
  • https://chatgpt-girlfriend.com/sitemap.xml

Sitemap

Present
Yes
URL count
3

Page title and metadata

Open Graph URL
https://chatgpt-girlfriend.com/
Page title
ChatGPT Girlfriend AI — Anime Virtual Girlfriend Chat, Free to Start
Open Graph type
website
Indexing directives
index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Open Graph image
https://chatgpt-girlfriend.com/wp-content/uploads/2026/10/hero-anime-companion.jpg
Open Graph title
ChatGPT Girlfriend AI — Anime Virtual Girlfriend Chat, Free to Start
Generator
WordPress 6.6.2
Open Graph site name
ChatGPT Girlfriend AI
Theme color
#0d0a1f
Description
ChatGPT Girlfriend AI: chat with anime virtual girlfriends who remember you, flirt back and are online 24/7. Pick a companion or create your own and start free.
Twitter card
summary_large_image
Open Graph description
ChatGPT Girlfriend AI: chat with anime virtual girlfriends who remember you, flirt back and are online 24/7. Pick a companion or create your own and start free.

Trackers

Requests
10
Observed services
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    2

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
8
TLS
33
Waiting
366
Connection
9
Download
1
Response time, ms
417

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
22703
CO₂, grams
0.0008
Cleaner than, %
54

DNS servers

Nameservers
  • IP address
    108.162.195.229
    Host
    ryan.ns.cloudflare.com
  • IP address
    108.162.192.184
    Host
    leia.ns.cloudflare.com
DNS zone
chatgpt-girlfriend.com

Location

IP address
2a06:98c1:3120::3
ASN
13335
Organization
CloudFLARENET-EU
City
London
Country
GB

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
chatgpt-girlfriend.com

DNS records

A
  • 188.114.97.3
  • 188.114.96.3
NS
  • ryan.ns.cloudflare.com
  • leia.ns.cloudflare.com
SOA
Primary nameserver
leia.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418676908
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2a06:98c1:3121::3
  • 2a06:98c1:3120::3

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2a06:98c1:3121::3
IP version
6

Redirects

Redirect chain
  • https://chatgpt-girlfriend.com

Page links

Internal links
8

Registration record

Registrar
PDR Ltd. d/b/a PublicDomainRegistry.com
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • leia.ns.cloudflare.com
  • ryan.ns.cloudflare.com

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=utf-8
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "chatgpt-girlfriend.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-28T20:44:53Z",
    "first": "2026-10-28T20:44:53Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 7451
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://chatgpt-girlfriend.com/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 3
}
Page title and metadata
{
    "ogUrl": "https://chatgpt-girlfriend.com/",
    "title": "ChatGPT Girlfriend AI — Anime Virtual Girlfriend Chat, Free to Start",
    "ogType": "website",
    "robots": "index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1",
    "ogImage": "https://chatgpt-girlfriend.com/wp-content/uploads/2026/10/hero-anime-companion.jpg",
    "ogTitle": "ChatGPT Girlfriend AI — Anime Virtual Girlfriend Chat, Free to Start",
    "generator": "WordPress 6.6.2",
    "ogSiteName": "ChatGPT Girlfriend AI",
    "themeColor": "#0d0a1f",
    "description": "ChatGPT Girlfriend AI: chat with anime virtual girlfriends who remember you, flirt back and are online 24/7. Pick a companion or create your own and start free.",
    "twitterCard": "summary_large_image",
    "ogDescription": "ChatGPT Girlfriend AI: chat with anime virtual girlfriends who remember you, flirt back and are online 24/7. Pick a companion or create your own and start free."
}
Trackers
{
    "requests": 10,
    "trackers": [
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 8,
        "tls": 33,
        "wait": 366,
        "connect": 9,
        "download": 1
    },
    "response_ms": 417
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 22703,
    "co2_grams": 0.0008,
    "cleaner_than": 54
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.195.229",
            "host": "ryan.ns.cloudflare.com"
        },
        {
            "ip": "108.162.192.184",
            "host": "leia.ns.cloudflare.com"
        }
    ],
    "zone": "chatgpt-girlfriend.com"
}
Location
{
    "ip": "2a06:98c1:3120::3",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "chatgpt-girlfriend.com"
}
DNS records
{
    "A": [
        "188.114.97.3",
        "188.114.96.3"
    ],
    "NS": [
        "ryan.ns.cloudflare.com",
        "leia.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"leia.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418676908, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2a06:98c1:3121::3",
        "2a06:98c1:3120::3"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2a06:98c1:3121::3",
    "family": 6
}
Redirects
{
    "chain": [
        "https://chatgpt-girlfriend.com"
    ]
}
Page links
{
    "internal_count": 8
}
Registration record
{
    "registrar": "PDR Ltd. d/b/a PublicDomainRegistry.com",
    "created": "2026-10-27T10:35:35Z",
    "updated": "2026-10-27T10:35:35Z",
    "expires": "2027-10-27T10:35:35Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "leia.ns.cloudflare.com",
        "ryan.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=utf-8"
    }
}

Questions about chatgpt-girlfriend.com

Is chatgpt-girlfriend.com legit?

PhishDestroy rates chatgpt-girlfriend.com as critical risk (72/100) from the recorded evidence; it was first recorded on 2026-10-28. Stored VirusTotal result: 1/92 engines flagged. malicious: 1. suspicious: 0. Analysis time (as stored): 2026-10-28T07:12:07Z. Retrieved (as stored): 2026-10-29T03:09:46Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is chatgpt-girlfriend.com safe to connect a wallet?

This report does not record which wallet requests chatgpt-girlfriend.com makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used chatgpt-girlfriend.com?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 5 captures

Cloudflare Radar 1 / 5 Used in the analysis Source file SHA-256: 103675d940b00604a95f69113dea9968498f18228ac0bdbb7f403ace6884b3a4 SHA-256 of the prepared copy given to the model: fd7afbac3ff5d1eec8870a7a1611693f8c85692d952907fd79a06c048a34d6b3
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://chatgpt-girlfriend.com/
Position1 / 5
Open capture Source Report Wayback Download
All capture links and hashes (5)
chatgpt-girlfriend.com: Suspected Chatgpt impersonation — 1/92 VirusTotal engines. PhishDestroy risk score 65/100 (high).
Social preview card chatgpt-girlfriend.com: Suspected Chatgpt impersonation — 1/92 VirusTotal engines. PhishDestroy risk score 65/100 (high). v 246f8fdfe4f8

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 76 report ↗
IP Context United Kingdom188.114.97.3 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar PDR US(US)
Abuse contactabuse-contact@publicdomainregistry.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for chatgpt-girlfriend.com →
RegistrationExpires Oct 27, 2027
Registrant countryUnited States VirusTotal WHOIS
Registrantedeae57e15fec50a374754e45373fcd8s@privacyprotect.org VirusTotal WHOIS
WHOIS statusclientTransferProhibited
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 28, 2026
DOM Analysisanalyzed Oct 29, 2026score 10/1001 brand signal
Submitted URLhttps://chatgpt-girlfriend.com/
Favicon Hash
Case ID
Observed page title
ChatGPT Girlfriend AI — Anime Virtual Girlfriend Chat, Free to Start
Automated brand references
Chatgpt
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 79 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United Kingdom188.114.97.3
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
CloudFLARENET-EU
Observed location
United KingdomLondon, GB
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • leia.ns.cloudflare.com
  • ryan.ns.cloudflare.com

SOA

  • nsname: leia.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2418676908
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-27 09:39:30
Valid until
2027-01-25 09:39:29
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprinte7fed8710591d5acb20eab52b1d9c185cd6adf0afa563d69ce5cf552c3df2a71
Certificate names · 2 SANs
  • *.chatgpt-girlfriend.com
  • chatgpt-girlfriend.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 · 188.114.97.3rapiddns.io

Latest Classified Outcome 2026-11-05 00:05:55 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-05 00:05:55 UTC
RDAP registration
Observed timeline last reachable: 2026-11-05 00:05:55 UTC last content: 2026-11-05 00:05:55 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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.chatgpt-girlfriend.comDomain record
Technologies · 7 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

1 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 1 detection
CRDF

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of chatgpt-girlfriend.com · checked Oct 28, 2026

84
Needs Work
Performance
FCP
2.74 s
First Contentful Paint
LCP
3.47 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
4.65 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: https://chatgpt-girlfriend.com/
ChatGPT Girlfriend AI — Anime Virtual Girlfriend Chat, Free to Start
ChatGPT Girlfriend AI: chat with anime virtual girlfriends who remember you, flirt back and are online 24/7. Pick a companion or create your own and start free.
Response
HTTP 200
HTML body
22.2 KB
Compressed
5.9 KB
Links
24 internal · 0 external
Detected technologies
jquerywordpresscloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: ef2eb433b1e206275c149570bb03419506259717c51e2ed5d75d8b02c3f41d8b
Open Graph title: ChatGPT Girlfriend AI — Anime Virtual Girlfriend Chat, Free to Start
Open Graph description: ChatGPT Girlfriend AI: chat with anime virtual girlfriends who remember you, flirt back and are online 24/7. Pick a companion or create your own and start free.
Twitter card: summary_large_image
Saved response-header values · 13
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a51cc71c6e1ad217-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Wed, 28 Oct 2026 20:44:19 GMT
Last-Modified
Tue, 27 Oct 2026 10:29:45 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=ZnFVaCgRStyCiyaYTSQYeGO1R%2B6I7IrJhJaDFDjwI4Dke13pcNB9P27XKo8dq8FmpQiru00lBi%2FvKLawrcj2qy2kyQsZYTKxT3dofWg7WwdOs90gSlrF5yMek0XjlgTkXXp6WGpfmpk
Server
cloudflare
Transfer-Encoding
chunked
Vary
accept-encoding

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

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content 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.

Captured network requests

Network requests: 17 SHA-256 hashes: 14 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 01:52 UTC.

Open this scan on URLScan 01a1843f-3261-712e-92d3-e47b1831148d ↗

Stored observation history10

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

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Availability monitor · Recorded state

    live_content→redirected

    http_redirect

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Availability monitor · Recorded state

    live_content

    content_served

Earlier observations 5
  1. Availability monitor · Recorded state

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. VirusTotal · Detection count

    0→1

    Engines added
    CRDF
    Engines removed
    None recorded
    Recorded vendor total
    1
  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Domain monitor · First collection record

    Reachable

All retained availability observations36

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-05 11:21:21.318386
    Evidence SHA-256
    547991b570db3c8269bee0185b7fa12df05c0b418f4b7a797fb4d0bb740e4f46
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-05 11:21:21.318386
    Evidence reason
  2. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-05 01:05:55.000000
    Evidence SHA-256
    b96ef931387a8803f4144489fd363d391ddeb6c40a780cfddf3551c63ffeaaa5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 01:05:55
    Evidence reason
    alive_content
  3. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-05 01:05:55.000000
    Evidence SHA-256
    b96ef931387a8803f4144489fd363d391ddeb6c40a780cfddf3551c63ffeaaa5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 01:05:55
    Evidence reason
    alive_content
  4. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 13:07:06.000000
    Evidence SHA-256
    2cd685671f3081fe8823257301e9256dd22ba78f9e9bc3c9c34feecdec9dee8c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-04 13:07:06
    Evidence reason
    alive_content
  5. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 13:07:06.000000
    Evidence SHA-256
    2cd685671f3081fe8823257301e9256dd22ba78f9e9bc3c9c34feecdec9dee8c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-04 13:07:06
    Evidence reason
    alive_content
  6. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 11:21:00.849465
    Evidence SHA-256
    94a9ae3d707b6cefa8168740bcb51c53137079a19bc0cd5bd77154e93c534a76
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-04 11:21:00.849465
    Evidence reason
  7. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-03 11:20:42.213040
    Evidence SHA-256
    7f511289ea6b6d1520a698f000d7fb3be1609f5f14dbf5ab5bf1c58eb4dbb974
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-03 11:20:42.213040
    Evidence reason
  8. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:30:53.000000
    Evidence SHA-256
    3133df648a71a728f93ba5af4caa8cee02a233b10281c214f3e4af2655cae744
    Evidence timestamp as recorded
    2026-11-02 12:30:53
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  9. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:30:53.000000
    Evidence SHA-256
    a5cecbc82c37505f7f29faeed852ca59f1c241f1d9d2b6b7279b3b1c6c952733
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 12:30:53
    Evidence reason
    alive_content
  10. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 11:20:40.834886
    Evidence SHA-256
    6b72dd67b3184766be6163de1e7b9604e36c85641b1d2618e2bdbe21069459a2
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 11:20:40.834886
    Evidence reason
  11. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 00:09:09.000000
    Evidence SHA-256
    85583dd9b5b2f4f2353b50fd4ef9891f6425f0c2a9c8b63ebf9a233643024775
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-02 00:09:09
    Evidence reason
    redirect
  12. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 00:09:09.000000
    Evidence SHA-256
    85583dd9b5b2f4f2353b50fd4ef9891f6425f0c2a9c8b63ebf9a233643024775
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-02 00:09:09
    Evidence reason
    redirect
  13. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:09:48.000000
    Evidence SHA-256
    f022a74ff0d83e3bf9329e45f9724bcf2b5e21c65ad4e4d144bbbd0e98a3af09
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:09:48
    Evidence reason
    alive_content
  14. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:09:48.000000
    Evidence SHA-256
    f022a74ff0d83e3bf9329e45f9724bcf2b5e21c65ad4e4d144bbbd0e98a3af09
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:09:48
    Evidence reason
    alive_content
  15. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 11:20:10.198716
    Evidence SHA-256
    b2987bb7a7acc32f1f9011b7a56a5a9a8539c203c0dded9abde43c0e22a9adeb
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 11:20:10.198716
    Evidence reason
  16. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:53:21.000000
    Evidence SHA-256
    fcf1fa93d6a9c9d89e2d31bd025d2043a65a647d6d22ca49612d4f8f1339b5dd
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:53:21
    Evidence reason
    alive_content
  17. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 03:53:21.000000
    Evidence SHA-256
    fcf1fa93d6a9c9d89e2d31bd025d2043a65a647d6d22ca49612d4f8f1339b5dd
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:53:21
    Evidence reason
    alive_content
  18. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:08:22.000000
    Evidence SHA-256
    bca16b28f203828b8b13413ce4c155737dc484e3c6f2cb354bb7efcf52590ece
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:08:22
    Evidence reason
    alive_content
  19. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:08:22.000000
    Evidence SHA-256
    bca16b28f203828b8b13413ce4c155737dc484e3c6f2cb354bb7efcf52590ece
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:08:22
    Evidence reason
    alive_content
  20. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:09:03.000000
    Evidence SHA-256
    44126a9d489c8e4a8681247dc8b52fa2fdf5611817552ea5731ef16a8a83ae7b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:09:03
    Evidence reason
    alive_content
  21. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:09:03.000000
    Evidence SHA-256
    44126a9d489c8e4a8681247dc8b52fa2fdf5611817552ea5731ef16a8a83ae7b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:09:03
    Evidence reason
    alive_content
  22. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 11:20:09.112163
    Evidence SHA-256
    b5c6551e799cfe4d3cb298004536f14652a7bd27158039d9a8bde93b0611124a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 11:20:09.112163
    Evidence reason
  23. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:30:13.000000
    Evidence SHA-256
    9b4339933691ff008c3518e6275beead903208c80843fda5821acc9afd8a75fe
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:30:13
    Evidence reason
    alive_content
  24. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:30:13.000000
    Evidence SHA-256
    9b4339933691ff008c3518e6275beead903208c80843fda5821acc9afd8a75fe
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:30:13
    Evidence reason
    alive_content
  25. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:06:30.000000
    Evidence SHA-256
    82b97a17fada1e743206646f97745976f5d6056ff83546bdc6f36c31f65683ad
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:06:30
    Evidence reason
    alive_content
  26. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:06:30.000000
    Evidence SHA-256
    82b97a17fada1e743206646f97745976f5d6056ff83546bdc6f36c31f65683ad
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:06:30
    Evidence reason
    alive_content
  27. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 05:03:05.462458
    Evidence SHA-256
    bbc8a7612fad967fe6394ef6e3533c42adb354b0403e4f596ca1b553348f1852
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 05:03:05.462458
    Evidence reason
  28. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:06:50.000000
    Evidence SHA-256
    379120ad51c599747fc245d376c27f666c882cba1f49ff37ab076931766fa953
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:06:50
    Evidence reason
    alive_content
  29. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:06:50.000000
    Evidence SHA-256
    379120ad51c599747fc245d376c27f666c882cba1f49ff37ab076931766fa953
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:06:50
    Evidence reason
    alive_content
  30. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:07:14.000000
    Evidence SHA-256
    e114f4100a3f455fb4c9a3285bfa3f54c89a0c443a518343b0ef602b48ce6ac1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:07:14
    Evidence reason
    alive_content
  31. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:07:14.000000
    Evidence SHA-256
    e114f4100a3f455fb4c9a3285bfa3f54c89a0c443a518343b0ef602b48ce6ac1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:07:14
    Evidence reason
    alive_content
  32. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 05:03:05.313035
    Evidence SHA-256
    e8d7330e223cce20a4540e7f3ccd4cc0f3b8c1f41fa08898b82c337408eae933
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 05:03:05.313035
    Evidence reason
  33. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 01:19:35.000000
    Evidence SHA-256
    d6cf9b8ffb195fad71a3f87f41edfc7b646393d666ebaac5364af56f84948357
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 01:19:35
    Evidence reason
    alive_content
  34. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 01:19:35.000000
    Evidence SHA-256
    d6cf9b8ffb195fad71a3f87f41edfc7b646393d666ebaac5364af56f84948357
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 01:19:35
    Evidence reason
    alive_content
  35. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 21:43:38.000000
    Evidence SHA-256
    a14e5b451f60ef9aa42556143c7ce1178b1d065c1ab192545d7a050edc1173b6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 21:43:38
    Evidence reason
  36. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 21:43:38.000000
    Evidence SHA-256
    a14e5b451f60ef9aa42556143c7ce1178b1d065c1ab192545d7a050edc1173b6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 21:43:38
    Evidence reason

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. Monitoring · in progress

Recorded events: 13. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    chatgpt-girlfriend.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Automated brand label: Chatgpt · Forensic Evidence Collected · Technical Analysis Recorded · VirusTotal detections +1 Recorded: 10 of 10
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 76
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 1/92
  • OTX Community References
    Community publication references on AlienVault OTX: 4. References are not vendor verdicts and are excluded from the evidence score.
  • Automated brand label: Chatgpt
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
  • VirusTotal detections +1
    New detections: +1 (0 → 1): CRDF
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: PDR Ltd. d/b/a PublicDomainRegistry.com. Abuse contacts: 1.
    • abuse-contact@publicdomainregistry.com
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

6 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Abuse report sent

    PD-A66CAFCDB97FEFEFA96A · Receipt 84093

    abuse-contact@publicdomainregistry.com
  3. Wayback Machine

    Page archived

    View source
  4. Added to PhishDestroy

    chatgpt-girlfriend.com

    View source
  5. URLScan

    Page captured

    View source
  6. VirusTotal

    1/92 engine detections

    View source
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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation
All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

chatgpt-girlfriend.com

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 1 det. ChainPatrol URLQuery Report stored SSL Labs Stored certificate dates valid CF Radar Open report OTX 4 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-A66CAFCDB97FEFEFA96A Recipient: abuse-contact@publicdomainregistry.com
PDF notice generated
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?

6 evidence signal groups linked 1 stored notification records Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

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 chatgpt-girlfriend.com)
  • 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

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/chatgpt-girlfriend.com"
  title="PhishDestroy threat report for chatgpt-girlfriend.com"
  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>