Skip to security report
Analytics Dashboard
Domain security and threat intelligence
monogr.ph favicon

monogr.ph

In short

monogr.ph is a blocklisted domain detected by PhishDestroy on 2026-09-23. Risk: critical (81/100). Status: Last known active. Hosting: Cloudflare, Inc. VirusTotal: 2/91 engines flag it. Do not enter credentials or connect a wallet.

“Monograph”

Resolved IP
188.114.97.3
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 2/91 Scam type: Impersonation
OTX: 5 refs Sep 23, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
2 / 91
engine detections
Google Safe Browsing
No threat flag
OTX
5
community references
Page captures
9
open gallery
Source evidenceVirusTotal 2 / 91 · OTX 5 references 5 sources

VirusTotal

2 / 91 engine detections

Open report

OTX

5 community references

Open report

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
2 / 91
OTX
5 community refs
Page captures
9
Page captures Source results

PhishDestroy threat report

Overview

monogr.ph is a phishing page that presents itself as Monograph. The page title reads simply "Monograph", and the short .ph domain is a compressed spelling of that name, built to pass a quick glance in a link or search result. It targets anyone who expects to reach the genuine Monograph service. PhishDestroy first flagged it on 2026-09-23, and it was still online and serving content on 2026-10-19.

How the scam works

Impersonation pages copy a brand's name and look so visitors trust them enough to act, usually by signing in, entering personal details or following prompts that lead to further fraud. Here the bare "Monograph" title and the near-match domain do that work. A visitor who believes they are on the real service and enters credentials hands them straight to the operators. Those credentials can then be used to take over the account or reused against other services that share the same password.

Evidence

Independent detection is thin so far. On 2026-10-06, VirusTotal showed 2 of 91 engines flagging the domain, Forcepoint ThreatSeeker and SOCRadar. AlienVault OTX lists it in 5 threat pulses, which means other researchers have tied it to tracked activity. PhishDestroy blocklists it. The low vendor count means most security products will not warn a visitor yet, so a clean scan should not be read as proof the site is safe.

Infrastructure

The domain resolves to 188.114.97.3, a Cloudflare address geolocated to Canada. Because Cloudflare acts as a reverse proxy, that IP belongs to Cloudflare's edge network and does not reveal the server that actually hosts the page. The site uses a Google Trust Services certificate (WE1), so the browser padlock appears as it would on a legitimate site. That padlock only means the connection is encrypted. It says nothing about who runs the site.

What to do

If you entered a password on monogr.ph, change it on the real Monograph service right away, along with any other account that uses the same password. Then turn on two-factor authentication and check for unfamiliar sessions or changes to your account settings. If you shared personal or payment details, watch for follow-up phishing and contact your bank where relevant. Defenders should block monogr.ph at DNS and web proxies, search logs for staff who visited it, and report it to Cloudflare so the content can be taken down.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review

Collected source details

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

URLScan · 2026-09-23T09:07:24Z

Observed: · Retrieved:

Uuid
01a0cd84-f6ee-716d-9c57-d91a9297f311
Final url
https://monogr.ph/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://monogr.ph/",
        "from": "http://monogr.ph/",
        "status": 307
    }
]
Ip
188.114.96.3
Contacted IP addresses
[
    "188.114.96.3"
]
Asns
[
    "13335"
]
Linked domains
[
    "app.notesnook.com",
    "help.notesnook.com",
    "twitter.com",
    "www.reddit.com",
    "t.me",
    "discord.com",
    "fosstodon.org",
    "notesnook.com",
    "blog.notesnook.com"
]
Social
[
    "https://twitter.com/notesnook",
    "https://t.me/notesnook",
    "https://discord.com/invite/zQBK97EE22"
]
Document hash
d5280f487710bc0fcb68c2136d0a786a43ed6f6fa2a16e321d7701ecac323185
Script hashes
[
    "cc7ae60ba01d558a4dc73b0548aba1cd99dfcf39882f8163d3246086f2e05c31",
    "8f9bab04ddddac43e30cad67c001d3b35a1aaa1deb9e99c1207c5f2adf8a6be9",
    "67bf02d449891735400b08132f7766eb4d38b6cab210953a2c2dd0eea1e70b38",
    "46375302c8dbcc45a2558e2cac30b8bdd4108449f9067e9198bea7a8731cfbe3",
    "c625e02dfd9a4974f07f6a1138a7261df41540fb4187c1ec96536aec79605b13",
    "a0b0ca8403b9f57581bc59d2d5593c31c14f4c733920a3ad9b7b2f7a69e5bafa",
    "759b9a96b6c498d6f5833eb0d4583c89c241f87df38166de482e68bacfbd3f5e",
    "a5c4674df74ceca467395bf9255d2332c6ed7efad5444559991aea127e04674d",
    "10f7abc201048b0a7a13e564a3eab578be000962ae8acb12d62cf35e1842b31a",
    "caf98c87de5ce6680419c49037988d7380a5401df8f86f98a4e3749146fff04c"
]
Globals
[
    "__remixContext",
    "__remixManifest",
    "__reactRouterVersion",
    "Buffer",
    "__remixRouteModules",
    "__remixRouter"
]
Cookies
[
    "cf_clearance"
]
Tls
{
    "san": [
        "monogr.ph",
        "*.monogr.ph"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "monogr.ph",
    "protocol": "QUIC",
    "valid_to": "2026-11-30T07:45:23Z",
    "valid_from": "2026-09-01T06:46:39Z"
}
Domain age days
968
Apex age days
968
Tls age days
22
Tls valid days
90
Requests
18
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": -38,
        "malicious": false
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31536000; includeSubDomains; preload",
    "content-security-policy": "script-src 'self' 'report-sample' 'nonce-dab5b815b6a99286c4d45eab1552def6' 'strict-dynamic'; connect-src 'self' https://notesnook.com/api/v1/reports/submit; form-action 'self'; object-src 'none'; bloc",
    "x-frame-options": "SAMEORIGIN",
    "x-content-type-options": "nosniff",
    "referrer-policy": "strict-origin-when-cross-origin",
    "permissions-policy": "camera=(), microphone=(), geolocation=()"
}
Cloudflare Radar · 2026-09-23T09:05:21Z

Observed: · Retrieved:

Uuid
1640fc03-1828-46e1-90d3-714935cd93ca
Final url
https://monogr.ph/
Status
200
History
[
    {
        "url": "https://monogr.ph/",
        "status": 200
    }
]
DOM structure hash
09a9e2767c7e9afa2e809e3c5083d8a0c1e08cd09c7221fc173890deeda64d37
Document hash
342be8a9f14b3e945d13ab5837eeae8c839c5cf3e3417c64a964f76b8d692d8c
Domain risks
[
    "Technology"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "monogr.ph",
        "type": "A",
        "value": "188.114.96.0"
    },
    {
        "name": "monogr.ph",
        "type": "A",
        "value": "188.114.97.0"
    },
    {
        "name": "monogr.ph",
        "type": "AAAA",
        "value": "2a06:98c1:3120::"
    },
    {
        "name": "monogr.ph",
        "type": "AAAA",
        "value": "2a06:98c1:3121::"
    }
]
Dnssec valid
false
Ip
188.114.96.0
VirusTotal · 2026-10-21T19:26:37Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 3,
    "suspicious": 0,
    "undetected": 34
}
Vendor labels
{
    "SOCRadar": "phishing",
    "desenmascara.me": "malicious",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Popularity
{
    "Majestic": 998918
}
First seen
2024-01-29T12:00:16Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.221.169"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3034::6815:3339"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "cora.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3036::ac43:dda9"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.51.57"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "cora.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "elmo.ns.cloudflare.com"
    }
]
Dns at
2026-10-21T19:31:42Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "monogr.ph",
        "*.monogr.ph"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "fca9610eb1b75469138df91a2bc273e6",
    "sha256": "f251b5495e1356746cd51b603b9e56a7d93591fba439f455b366faa31a1b21f5",
    "subject": "monogr.ph",
    "valid_to": "2026-11-30T07:45:23Z",
    "valid_from": "2026-09-01T06:46:39Z"
}

Questions about monogr.ph

Is monogr.ph legit?

No. PhishDestroy classifies monogr.ph as a blocklisted domain (risk: critical, 81/100); it was first detected on 2026-09-23. VirusTotal: 2/91 engines flag it. Treat the site as unsafe.

Is monogr.ph safe to connect a wallet?

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

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

Extracted from stored page analysis

Observed indicators

0 wallet · 1 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

Telegram
https://t.me/notesnookStored page reference

IoC extraction recorded 2026-09-24 04:00:16 UTC

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 9 captures

Primary capture 1 / 9
SourcePrimary capture
Recorded2026-09-23 09:08 UTC
StateStored capture
Position1 / 9
Open capture Wayback Download

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
Observed indicators0 wallet · 1 Telegram — full values ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedSep 23, 2026
DOM Analysisanalyzed Sep 23, 2026score 81/100
IoC Extractionscanned Sep 24, 20260 wallet · 1 Telegram IoC
Submitted URLhttp://monogr.ph/
Favicon Hash
Observed page title
Monograph
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 38 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • cora.ns.cloudflare.com
  • elmo.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-09-01 06:46:39
Valid until
2026-11-30 07:45:23
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-11 04:03:19 UTC
Collection source
PhishDestroy collector
Certificate fingerprintf251b5495e1356746cd51b603b9e56a7d93591fba439f455b366faa31a1b21f5
Certificate names · 2 SANs
  • monogr.ph
  • *.monogr.ph

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-10-22 10:30:30 UTC

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-10-22 10:30:30 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:30:30 UTC last content: 2026-10-22 10:30:30 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 · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

2 / 91 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 2 detections
Forcepoint ThreatSeeker
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 monogr.ph · checked Sep 23, 2026

100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
0.76s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.15s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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.

Stored observation history21

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→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 16
  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  14. Availability monitor · Recorded state

    live_content

    content_served

  15. VirusTotal · Detection count

    0→2

  16. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    2/91 engine detections

    View source
  3. AlienVault OTX

    5 community references

    View source
  4. URLScan

    Page captured

    View source
  5. Added to PhishDestroy

    monogr.ph

    View source

Check for cloaking

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

monogr.ph

Evidence & External Reports

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

Were You Affected by This Site?

4 evidence signal groups linked 0 stored notification records Last known active

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

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 monogr.ph)
  • 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

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.

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