Skip to security report
This domain has been flagged as malicious
Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
invitemeetingapp.com favicon

invitemeetingapp.com

In short

invitemeetingapp.com is a blocklisted domain detected by PhishDestroy on 2026-10-27.

“www.invitemeetingapp.com”

Registrar
United StatesNamecheap
Resolved IP
United States162.255.119.236Namecheap
First observed
Oct 27, 2026
PhishDestroy assessment Critical
90/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Stored blocklist matches: 2
VirusTotal
engine detections ·
Blocklist matches
MetaMask, SEAL
OTX
community references
URLScan
engine verdict · score 51
Page captures
open gallery
Reports sent
view timeline
OTX: 3 refs Oct 27, 2026 1 Report Sent
X Telegram API

Analysis

Domain summary

invitemeetingapp.com is a blocklisted domain detected by PhishDestroy on 2026-10-27. Risk: critical (90/100). Registrar: Namecheap. Status: Last known active. Hosting: Namecheap. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
0 / 92
Blocklist matches
2
Hosting
United States162.255.119.236Namecheap
Registrar
United StatesNamecheap
OTX
3 community refs
Page captures
4

PhishDestroy threat report

Overview

PhishDestroy added invitemeetingapp.com to its internal blocklist on 2026-10-27 following an admin report that noted the domain was newly registered and appeared to promote Namecheap auction services. The recorded page title was "www.invitemeetingapp.com" and the HTTP response returned status 200 on the same date. No phishing, scam or other malicious content was observed on the page.

How the scam works

The available evidence does not demonstrate a specific scam technique; the domain is simply flagged as suspicious. In general, newly registered domains with generic titles can be used for phishing, credential harvesting, or fraudulent offers, but none of those behaviors were identified on this site.

Evidence

VirusTotal scanned the domain on 2026-10-27 and reported 0 detections out of 92 engines. Google Safe Browsing checked on 2026-10-27 and did not flag the URL. urlscan captured the site on 2026-10-27; its overall verdict was non‑malicious, while its machine‑learning engine marked it as malicious with a score of 51 and tags urlscan‑ml. External blocklists MetaMask and SEAL listed the domain, and OTX recorded 3 pulses referencing it. PhishDestroy’s internal blocklist also contains the domain.

Infrastructure

The domain was registered with NameCheap Inc on 2026-10-25. The recorded DNS data on 2026-10-27 showed an A record of 162.255.119.236, which belonged to ASN 22612 and was listed as belonging to Namecheap, located in Los Angeles, US, and an open port 80 for HTTP. Nameservers were dns1.registrar-servers.com and dns2.registrar-servers.com, and MX records pointed to registrar‑forwarded mail servers.

What to do

Visitors should avoid entering credentials or personal data on the site; if any credentials were submitted, change the associated passwords promptly. No wallet‑related actions are applicable because wallet recommendations are disabled. Defenders should log any traffic to invitemeetingapp.com, consider blocking the domain at the network perimeter, and monitor for future activity.

Source evidenceVirusTotal 0 / 92 · OTX 3 references 9 sources

Cloudflare Radar

Suspicious

Open report
Cloudflare RadarOriginal source recordObserved: 9 fields

Observed: · Retrieved:

Report ID

cfb32b65-367a-4525-9612-19c57488dd48

Final URL

https://invitemeetingapp.com/

Navigation history

  • URL
    https://invitemeetingapp.com/
    Status
    0

DOM structure hash

222edc6576ce4f900a55dd02c5523f77c5fa64ee8b4e540f3ff8452026c169a8

Domain risk categories

  • Newly Seen Domains
  • Security Risks
  • New Domains

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    invitemeetingapp.com
    Type
    A
    Value
    162.255.119.236

DNSSEC valid

No

Registration record

Registrar
NameCheap, Inc.
Registered
Updated
Expires
Nameservers
  • dns1.registrar-servers.com
  • dns2.registrar-servers.com
Original source fields · JSON
Uuid
cfb32b65-367a-4525-9612-19c57488dd48
Final url
https://invitemeetingapp.com/
History
[
    {
        "url": "https://invitemeetingapp.com/",
        "status": 0
    }
]
DOM structure hash
222edc6576ce4f900a55dd02c5523f77c5fa64ee8b4e540f3ff8452026c169a8
Domain risks
[
    "Newly Seen Domains",
    "Security Risks",
    "New Domains"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "invitemeetingapp.com",
        "type": "A",
        "value": "162.255.119.236"
    }
]
Dnssec valid
false
Registration record
{
    "registrar": "NameCheap, Inc.",
    "created": "2026-10-25T16:58:36Z",
    "updated": "2026-10-25T16:58:40Z",
    "expires": "2027-10-25T16:58:36Z",
    "nameservers": [
        "dns1.registrar-servers.com",
        "dns2.registrar-servers.com"
    ]
}

URLScan

Malicious · engine verdict · score 51

SHA-256 867a59ecb19de5cd6fa12f88d1599a65a2512ba9ed372daded289641555e65ec

Open report
URLScanOriginal source recordObserved: 9 fields

Observed: · Retrieved:

Report ID

01a17b9c-b6ac-75f1-906d-06376bea6dcf

Final URL

http://invitemeetingapp.com/

Redirects

  • To
    https://invitemeetingapp.com/
    From
    http://invitemeetingapp.com/
    Status
    307
  • To
    http://invitemeetingapp.com/
    From
    https://invitemeetingapp.com/
    Status
    307
  • To
    http://www.invitemeetingapp.com/
    From
    http://invitemeetingapp.com/
    Status
    302
  • To
    https://www.invitemeetingapp.com/
    From
    http://www.invitemeetingapp.com/
    Status
    307
  • To
    http://www.invitemeetingapp.com/
    From
    https://www.invitemeetingapp.com/
    Status
    307

Contacted domains

  • www.invitemeetingapp.com

JavaScript globals

  • assert
  • getRequiredElement
  • P
  • S
  • getRandomNum
  • getTimeStamp
  • Dimensions
  • Config$2
  • getGlobalConfig
  • setGlobalConfig
  • Config$1
  • Config
  • setMaxGapCoefficient
  • setMaxObstacleLength
  • Status
  • A11yStrings
  • RunnerClasses
  • RunnerSounds
  • RunnerEvents
  • updateCanvasScaling
  • getA11yString
  • vibrate
  • createCanvas
  • decodeBase64ToArrayBuffer
  • createAdjustedCollisionBox
  • drawCollisionBoxes
  • boxCompare
  • toggleHelpBox
  • diagnoseErrors
  • portalSignin
  • updateForDnsProbe
  • getMainFrameErrorCssClass
  • getMainFrameErrorIconCssClass
  • getSubFrameErrorIconCssClass
  • shouldShowSuggestionsSummaryList
  • getSuggestionsSummaryItemCssClass
  • reloadButtonClick
  • downloadButtonClick
  • detailsButtonClick
  • setAutoFetchState

Domain age, days

0

Registered domain age, days

0

Page requests

5

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
51
Malicious
Yes
Overall verdict
Score
0
Malicious
No
Original source fields · JSON
Uuid
01a17b9c-b6ac-75f1-906d-06376bea6dcf
Final url
http://invitemeetingapp.com/
Redirects
[
    {
        "to": "https://invitemeetingapp.com/",
        "from": "http://invitemeetingapp.com/",
        "status": 307
    },
    {
        "to": "http://invitemeetingapp.com/",
        "from": "https://invitemeetingapp.com/",
        "status": 307
    },
    {
        "to": "http://www.invitemeetingapp.com/",
        "from": "http://invitemeetingapp.com/",
        "status": 302
    },
    {
        "to": "https://www.invitemeetingapp.com/",
        "from": "http://www.invitemeetingapp.com/",
        "status": 307
    },
    {
        "to": "http://www.invitemeetingapp.com/",
        "from": "https://www.invitemeetingapp.com/",
        "status": 307
    }
]
Contacted domains
[
    "www.invitemeetingapp.com"
]
Globals
[
    "assert",
    "getRequiredElement",
    "P",
    "S",
    "getRandomNum",
    "getTimeStamp",
    "Dimensions",
    "Config$2",
    "getGlobalConfig",
    "setGlobalConfig",
    "Config$1",
    "Config",
    "setMaxGapCoefficient",
    "setMaxObstacleLength",
    "Status",
    "A11yStrings",
    "RunnerClasses",
    "RunnerSounds",
    "RunnerEvents",
    "updateCanvasScaling",
    "getA11yString",
    "vibrate",
    "createCanvas",
    "decodeBase64ToArrayBuffer",
    "createAdjustedCollisionBox",
    "drawCollisionBoxes",
    "boxCompare",
    "toggleHelpBox",
    "diagnoseErrors",
    "portalSignin",
    "updateForDnsProbe",
    "getMainFrameErrorCssClass",
    "getMainFrameErrorIconCssClass",
    "getSubFrameErrorIconCssClass",
    "shouldShowSuggestionsSummaryList",
    "getSuggestionsSummaryItemCssClass",
    "reloadButtonClick",
    "downloadButtonClick",
    "detailsButtonClick",
    "setAutoFetchState"
]
Domain age days
0
Apex age days
0
Requests
5
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 51,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a17b9c-b6ac-75f1-906d-06376bea6dcf
score
null
malicious
null
result_at
null
enriched_at
2026-10-27T09:14:01Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-10-27 10:14:01"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

VirusTotal

0 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
0
Malicious
0
Suspicious
0
Undetected
92

Reputation score

0

Registrar

NAMECHEAP INC

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    1800
    Type
    TXT
    Value
    v=spf1 include:spf.efwd.registrar-servers.com ~all
  • TTL, seconds
    1800
    Type
    MX
    Value
    eforward4.registrar-servers.com
    Priority
    15
  • TTL, seconds
    1800
    Type
    MX
    Value
    eforward2.registrar-servers.com
    Priority
    10
  • TTL, seconds
    1800
    Type
    MX
    Value
    eforward1.registrar-servers.com
    Priority
    10
  • TTL, seconds
    1800
    Type
    NS
    Value
    dns2.registrar-servers.com
  • TTL, seconds
    1800
    Type
    NS
    Value
    dns1.registrar-servers.com
  • TTL, seconds
    1800
    Type
    MX
    Value
    eforward3.registrar-servers.com
    Priority
    10
  • TTL, seconds
    3601
    Type
    SOA
    Responsible mailbox
    hostmaster.registrar-servers.com
    Value
    dns1.registrar-servers.com
  • TTL, seconds
    1800
    Type
    MX
    Value
    eforward5.registrar-servers.com
    Priority
    20
  • TTL, seconds
    1800
    Type
    A
    Value
    162.255.119.236

DNS records observed

Registration record

Registrar
NAMECHEAP INC
Registrar IANA ID
1068
Registrar URL
http://www.namecheap.com
Registered
Updated
1-01-01T00:00:00Z
Expires
Status
  • addPeriod
  • clientTransferProhibited
Nameservers
  • dns1.registrar-servers.com
  • dns2.registrar-servers.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • client transfer prohibited
  • add period
Registry events
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 0,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 92
}
Reputation
0
Registrar
NAMECHEAP INC
Created
2026-10-25T16:58:36Z
Expires
2027-10-25T16:58:36Z
Updated
2026-10-25T16:58:40Z
First seen
2026-10-27T04:21:20Z
DNS records
[
    {
        "ttl": 1800,
        "type": "TXT",
        "value": "v=spf1 include:spf.efwd.registrar-servers.com ~all"
    },
    {
        "ttl": 1800,
        "type": "MX",
        "value": "eforward4.registrar-servers.com",
        "priority": 15
    },
    {
        "ttl": 1800,
        "type": "MX",
        "value": "eforward2.registrar-servers.com",
        "priority": 10
    },
    {
        "ttl": 1800,
        "type": "MX",
        "value": "eforward1.registrar-servers.com",
        "priority": 10
    },
    {
        "ttl": 1800,
        "type": "NS",
        "value": "dns2.registrar-servers.com"
    },
    {
        "ttl": 1800,
        "type": "NS",
        "value": "dns1.registrar-servers.com"
    },
    {
        "ttl": 1800,
        "type": "MX",
        "value": "eforward3.registrar-servers.com",
        "priority": 10
    },
    {
        "ttl": 3601,
        "type": "SOA",
        "rname": "hostmaster.registrar-servers.com",
        "value": "dns1.registrar-servers.com"
    },
    {
        "ttl": 1800,
        "type": "MX",
        "value": "eforward5.registrar-servers.com",
        "priority": 20
    },
    {
        "ttl": 1800,
        "type": "A",
        "value": "162.255.119.236"
    }
]
Dns at
2026-10-27T04:21:20Z
Registration record
{
    "registrar": "NAMECHEAP INC",
    "registrar_iana_id": "1068",
    "registrar_url": "http://www.namecheap.com",
    "created": "2026-10-25T16:58:36Z",
    "updated": "1-01-01T00:00:00Z",
    "expires": "2027-10-25T16:58:36Z",
    "status": [
        "addPeriod",
        "clientTransferProhibited"
    ],
    "nameservers": [
        "dns1.registrar-servers.com",
        "dns2.registrar-servers.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited",
        "add period"
    ],
    "events": {
        "registration": "2026-10-25T16:58:36Z",
        "registrar expiration": "2027-10-25T16:58:36Z",
        "last update of RDAP database": "2026-10-27T04:21:20Z"
    }
}
Separate source record · 0 malicious + 0 suspicious / 92 · 2026-10-27 04:20:45 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-27T04:20:45Z
fetched_at
2026-10-27T05:01:28Z
stats
{"timeout":0,"harmless":0,"malicious":0,"suspicious":0,"undetected":92}

OTX

3 community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

90 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 0 / 100 · 2026-10-27T05:08:00Z

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
0
analyzed_at
2026-10-27T05:08:00Z
source_timestamp
2026-10-27 06:08:00
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
invitemeetingapp.com — Suspicious Domain
ai_description
PhishDestroy flagged invitemeetingapp.com as a suspicious domain after an admin report; the site showed a generic title and no malicious content on 2026-10-27.
ai_generated_at
2026-10-27T05:05:19Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider 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: 10 fields

Mail configuration

MX records
  • eforward3.registrar-servers.com
  • eforward4.registrar-servers.com
  • eforward5.registrar-servers.com
  • eforward1.registrar-servers.com
  • eforward2.registrar-servers.com
SPF record
v=spf1 include:spf.efwd.registrar-servers.com ~all
SPF lookups
1

CAA records

Domain
invitemeetingapp.com

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Ports

Open ports
  • 80

DNS servers

Nameservers
  • IP address
    156.154.132.200
    Host
    dns1.registrar-servers.com
  • IP address
    156.154.133.200
    Host
    dns2.registrar-servers.com
DNS zone
invitemeetingapp.com

Location

IP address
162.255.119.236
ASN
22612
Organization
Namecheap
City
Los Angeles
Country
US

DNS records

A
  • 162.255.119.236
MX
  • Mail server
    eforward5.registrar-servers.com
    Priority
    20
  • Mail server
    eforward1.registrar-servers.com
    Priority
    10
  • Mail server
    eforward2.registrar-servers.com
    Priority
    10
  • Mail server
    eforward3.registrar-servers.com
    Priority
    10
  • Mail server
    eforward4.registrar-servers.com
    Priority
    15
NS
  • dns1.registrar-servers.com
  • dns2.registrar-servers.com
SOA
Primary nameserver
dns1.registrar-servers.com
Hostmaster
hostmaster.registrar-servers.com
Serial
1792947524
Refresh, seconds
43200
Retry, seconds
3600
Expiry, seconds
604800
Minimum TTL, seconds
3601
TXT
  • v=spf1 include:spf.efwd.registrar-servers.com ~all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
162.255.119.236
IP version
4

Registration record

Registrar
NameCheap, Inc.
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • dns1.registrar-servers.com
  • dns2.registrar-servers.com
Original source fields · JSON
Mail configuration
{
    "mx": [
        "eforward3.registrar-servers.com",
        "eforward4.registrar-servers.com",
        "eforward5.registrar-servers.com",
        "eforward1.registrar-servers.com",
        "eforward2.registrar-servers.com"
    ],
    "spf": "v=spf1 include:spf.efwd.registrar-servers.com ~all",
    "spf_lookups": 1
}
Caa records
{
    "domain": "invitemeetingapp.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Ports
{
    "open": [
        80
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "156.154.132.200",
            "host": "dns1.registrar-servers.com"
        },
        {
            "ip": "156.154.133.200",
            "host": "dns2.registrar-servers.com"
        }
    ],
    "zone": "invitemeetingapp.com"
}
Location
{
    "ip": "162.255.119.236",
    "asn": "22612",
    "org": "Namecheap",
    "city": "Los Angeles",
    "country": "US"
}
DNS records
{
    "A": [
        "162.255.119.236"
    ],
    "MX": [
        "{\"exchange\": \"eforward5.registrar-servers.com\", \"priority\": 20}",
        "{\"exchange\": \"eforward1.registrar-servers.com\", \"priority\": 10}",
        "{\"exchange\": \"eforward2.registrar-servers.com\", \"priority\": 10}",
        "{\"exchange\": \"eforward3.registrar-servers.com\", \"priority\": 10}",
        "{\"exchange\": \"eforward4.registrar-servers.com\", \"priority\": 15}"
    ],
    "NS": [
        "dns1.registrar-servers.com",
        "dns2.registrar-servers.com"
    ],
    "SOA": "{\"nsname\": \"dns1.registrar-servers.com\", \"hostmaster\": \"hostmaster.registrar-servers.com\", \"serial\": 1792947524, \"refresh\": 43200, \"retry\": 3600, \"expire\": 604800, \"minttl\": 3601}",
    "TXT": [
        "v=spf1 include:spf.efwd.registrar-servers.com ~all"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "162.255.119.236",
    "family": 4
}
Registration record
{
    "registrar": "NameCheap, Inc.",
    "created": "2026-10-25T16:58:36Z",
    "updated": "2026-10-25T16:58:40Z",
    "expires": "2027-10-25T16:58:36Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "dns1.registrar-servers.com",
        "dns2.registrar-servers.com"
    ]
}

Questions about invitemeetingapp.com

Is invitemeetingapp.com legit?

No. PhishDestroy classifies invitemeetingapp.com as a blocklisted domain (risk: critical, 90/100); it was first detected on 2026-10-27. Treat the site as unsafe.

Is invitemeetingapp.com safe to connect a wallet?

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

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

Explore

Blocklist matchesMetaMask · PhishDestroy · SEAL · no match in the other 9 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 4 captures

All capture links and hashes (4)
invitemeetingapp.com: Crypto scam — Blocked by MetaMask, flagged by SEAL. PhishDestroy risk score 90/100 (critical).
Social preview card invitemeetingapp.com: Crypto scam — Blocked by MetaMask, flagged by SEAL. PhishDestroy risk score 90/100 (critical). v 1eb629cd20f4

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 51 report ↗
IP Reputation United States162.255.119.236 abuse score 0/100 0 reports checked Oct 27, 2026 last reported
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Namecheap US(US)
Hosting abuse contact abuse@namecheap.com Namecheap · AS22612
RegistrationExpires Oct 25, 2027
Registrant countryUnited States VirusTotal WHOIS
Registrant3b5f76ecd769308f9e26ce17f72763a7s@withheldforprivacy.com VirusTotal WHOIS
HTTP Status302 Found (Temporary)
Technical detailsProvenance & timestamps
First DetectedOct 27, 2026
DOM Analysisanalyzed Oct 27, 2026score 90/100
Submitted URLhttp://invitemeetingapp.com/
Case ID
Observed page title
www.invitemeetingapp.com

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States162.255.119.236
Network ASN
AS22612
Organization
Namecheap
Observed location
United StatesLos Angeles, US
Server header
nginx/1.28.3 (Ubuntu)

Nameservers 2

  • dns1.registrar-servers.com
  • dns2.registrar-servers.com

SOA

  • nsname: dns1.registrar-servers.com
  • hostmaster: hostmaster.registrar-servers.com
  • serial: 1792947524
  • refresh: 43200
  • retry: 3600
  • expire: 604800
  • minttl: 3601

Registrar abuse contact VirusTotal WHOIS

Mail routing 5 MX records

  • eforward4.registrar-servers.compriority 15
  • eforward2.registrar-servers.compriority 10
  • eforward1.registrar-servers.compriority 10
  • eforward3.registrar-servers.compriority 10
  • eforward5.registrar-servers.compriority 20

Location describes the IP network.

Latest Classified Outcome 2026-10-27 12:31:06 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Unreachable Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-27 12:31:06 UTC
RDAP registration
Observed timeline last reachable: 2026-10-27 04:28:50 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.
Report This Domain Submit evidence & help protect others
Stored Capture Evidence 1 snapshot

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

Archived HTTP response HTTP 200
Requested URL: http://invitemeetingapp.com/
Final URL: http://www.invitemeetingapp.com/
Response
HTTP 200
HTML body
2.9 KB
Compressed
1.2 KB
Links
0 internal · 4 external
Detected technologies
nginx
Selected response headers
Server: nginx/1.28.3 (Ubuntu)
Content-Type: text/html
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 9
Connection
close
Content-Encoding
gzip
Content-Type
text/html
Date
Tue, 27 Oct 2026 04:29:18 GMT
Etag
W/"6a6b771b-b93"
Last-Modified
Thu, 30 Jul 2026 16:08:59 GMT
Server
nginx/1.28.3 (Ubuntu)
Transfer-Encoding
chunked
Vary
Accept-Encoding

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

Registration & observation details1

Availability observations

Last reachable observation

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

Stored observation history2

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

    redirected

    http_redirect

  2. Domain monitor · First collection record

    Reachable

All retained availability observations4

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. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    302
    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-10-27 13:31:06.000000
    Evidence SHA-256
    a981463e352a60366582157f0be729b493f269fd5ecc6aa1fd8b68d2f75051eb
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-27 13:31:06
    Evidence reason
    redirect
  2. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    302
    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-10-27 13:31:06.000000
    Evidence SHA-256
    a981463e352a60366582157f0be729b493f269fd5ecc6aa1fd8b68d2f75051eb
    HTTP probe value as recorded
    302
    Evidence timestamp as recorded
    2026-10-27 13:31:06
    Evidence reason
    redirect
  3. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    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-27 05:28:50.000000
    Evidence SHA-256
    0b6d33b5edf07577578327615781f557e1b7fb38da30261348ed82ab3c09857b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 05:28:50
    Evidence reason
  4. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    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-27 05:28:50.000000
    Evidence SHA-256
    0b6d33b5edf07577578327615781f557e1b7fb38da30261348ed82ab3c09857b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 05:28:50
    Evidence reason

Threat Response Pipeline

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

Recorded events: 10. 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
    invitemeetingapp.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Blocklist Detection · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 51
  • 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.
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • OTX Community References
    Community publication references on AlienVault OTX: 3. References are not vendor verdicts and are excluded from the evidence score.
  • 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.
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: NAMECHEAP INC. Abuse contacts: 1.
    • abuse@namecheap.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

5 entries
  1. AlienVault OTX

    3 community references

    View source
  2. VirusTotal

    0/92 engine detections

    View source
  3. Abuse report sent

    PD-20261027-11C27C · Receipt 83673

    abuse@namecheap.com
  4. Added to PhishDestroy

    invitemeetingapp.com

    View source
  5. URLScan

    Page captured

    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.

Check for cloaking

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

invitemeetingapp.com

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261027-11C27C Recipient: abuse@namecheap.com
Page title stored with report: New Private Tab
Blocklist hits included with submission: MetaMask, SEAL
PDF notice generated Notice text archived (289 characters)
Abuse notice text as sent to the provider
Registrar: Namecheap Inc (United States)
Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
Deep Analysis
Help & reporting

Were You Affected by This Site?

5 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.

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

Official reporting routes

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.

Report to Your Local Authorities

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

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

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.

  • 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 invitemeetingapp.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

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.

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