Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 9. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
law993.github.io favicon

law993.github.io

In short

PhishDestroy describes law993.github.io, a GitHub Pages 404 error page stating that no site exists at this address.

Review the evidence
Registrar
GitHub
Resolved IP
United States185.199.108.153Fastly, Inc. · CDN
First observed
Oct 31, 2026
PhishDestroy assessment Critical
77/100
Evidence score
Availability Server error The latest stored response was inconclusive Observed HTTP probe
Risk signals
VirusTotal detections: 9/92 Stored blocklist matches: 1
VirusTotal
9 / 92
engine detections ·
Blocklist matches
1
PhishFeed
URLScan
Malicious
Page captures
7
open gallery
Oct 31, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy describes law993.github.io, a GitHub Pages 404 error page stating that no site exists at this address.

Critical
Status
Server error
VirusTotal
9 / 92
Blocklist matches
1
Hosting
United States185.199.108.153Fastly, Inc. · CDN
Registrar
GitHub
Page captures
7
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page at law993.github.io is a GitHub Pages 404 error page, displaying a large "404" heading and the message "There isn't a GitHub Pages site here." Below that, it offers a link to read the full documentation on setting up GitHub Pages for a repository, organization, or user account, along with links to GitHub Status and @githubstatus. The page contains no login form or credential fields, and the only interaction offered is following the documentation link.

The stored VirusTotal domain result reports 9 detections out of 92 engines. DNS8 reported "suspicious"; G-Data reported "phishing".

Source evidenceVirusTotal 9 / 92 6 sources

VirusTotal

9 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
51
Malicious
8
Suspicious
1
Undetected
32

Vendor labels

DNS8
suspicious
G-Data
phishing
Sophos
phishing
Webroot
malicious
Emsisoft
phishing
Fortinet
phishing
Netcraft
malicious
SOCRadar
phishing
alphaMountain.ai
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

MarkMonitor Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    3600
    Type
    CAA
    Value
    letsencrypt.org
  • TTL, seconds
    3600
    Type
    AAAA
    Value
    2606:50c0:8001::153
  • TTL, seconds
    3600
    Type
    CAA
    Value
    sectigo.com
  • TTL, seconds
    3600
    Type
    CAA
    Value
    digicert.com
  • TTL, seconds
    3600
    Type
    CAA
    Value
    letsencrypt.org
  • TTL, seconds
    3600
    Type
    A
    Value
    185.199.108.153
  • TTL, seconds
    3600
    Type
    A
    Value
    185.199.110.153
  • TTL, seconds
    3600
    Type
    AAAA
    Value
    2606:50c0:8000::153
  • TTL, seconds
    3600
    Type
    A
    Value
    185.199.109.153
  • TTL, seconds
    3600
    Type
    CAA
    Value
    digicert.com
  • TTL, seconds
    3600
    Type
    A
    Value
    185.199.111.153
  • TTL, seconds
    3600
    Type
    AAAA
    Value
    2606:50c0:8002::153
  • TTL, seconds
    3600
    Type
    CAA
    Value
    sectigo.com
  • TTL, seconds
    3600
    Type
    AAAA
    Value
    2606:50c0:8003::153

DNS records observed

JARM fingerprint

29d3fd00029d29d00041d41d00041d6b5eefa2404a56c2ced79a0d16afe36c

Certificate

Subject alternative names
  • *.github.com
  • *.github.io
  • *.githubusercontent.com
  • github.com
  • github.io
  • githubusercontent.com
Issuer
Let's Encrypt / YR1
Serial
6a65e5d3279ba564a4de74eb5d64478dbb8
SHA-256
f2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856
Subject
*.github.io
Valid until
Valid from

Registration record

Registrar
MarkMonitor Inc.
Registrar IANA ID
292
Registrar URL
http://www.markmonitor.com
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • dns1.p05.nsone.net
  • dns2.p05.nsone.net
  • dns3.p05.nsone.net
  • ns-1622.awsdns-10.co.uk
  • ns-692.awsdns-22.net
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 51,
    "malicious": 8,
    "suspicious": 1,
    "undetected": 32
}
Vendor labels
{
    "DNS8": "suspicious",
    "G-Data": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "SOCRadar": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
MarkMonitor Inc.
Created
2013-03-08T19:41:10Z
Expires
2027-03-08T19:12:48Z
Updated
2026-08-12T09:08:04Z
First seen
2026-10-30T17:06:18Z
DNS records
[
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "letsencrypt.org"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8001::153"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "sectigo.com"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "digicert.com"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "letsencrypt.org"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.108.153"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.110.153"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8000::153"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.109.153"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "digicert.com"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.111.153"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8002::153"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "sectigo.com"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8003::153"
    }
]
Dns at
2026-10-31T10:44:06Z
Jarm
29d3fd00029d29d00041d41d00041d6b5eefa2404a56c2ced79a0d16afe36c
Certificate
{
    "san": [
        "*.github.com",
        "*.github.io",
        "*.githubusercontent.com",
        "github.com",
        "github.io",
        "githubusercontent.com"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "6a65e5d3279ba564a4de74eb5d64478dbb8",
    "sha256": "f2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856",
    "subject": "*.github.io",
    "valid_to": "2026-12-29T23:44:45Z",
    "valid_from": "2026-09-30T23:44:46Z"
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "registrar_iana_id": "292",
    "registrar_url": "http://www.markmonitor.com",
    "created": "2013-03-08T19:12:48Z",
    "updated": "2025-02-25T20:53:31Z",
    "expires": "2027-03-08T00:00:00Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "dns1.p05.nsone.net",
        "dns2.p05.nsone.net",
        "dns3.p05.nsone.net",
        "ns-1622.awsdns-10.co.uk",
        "ns-692.awsdns-22.net"
    ],
    "dnssec": "unsigned"
}
Separate source record · 8 malicious + 1 suspicious / 92 · 2026-10-31 10:43:53 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-31T10:43:53Z
fetched_at
2026-10-31T23:16:23Z
stats
{"timeout":0,"harmless":51,"malicious":8,"suspicious":1,"undetected":32}

URLScan

Malicious

SHA-256 954ee84118d6983fc0a4a7fa1054203106aae0bd302b92d7990b3a040dc45fe3

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a1941c-dab7-710a-9f21-2acb30bfc041

Final URL

https://law993.github.io/123/

HTTP response

200

Redirect type

same-domain

Redirects

  • To
    https://law993.github.io/123
    From
    http://law993.github.io/123
    Status
    307
  • To
    https://law993.github.io/123/
    From
    https://law993.github.io/123
    Status
    301

IP address

2606:50c0:8002::153

Contacted domains

  • cdnjs.cloudflare.com

Contacted IP addresses

  • 104.17.25.14
  • 2606:50c0:8002::153

Autonomous systems (ASN)

  • 13335
  • 54113

Server countries

  • US

Linked domains

  • apps.apple.com
  • play.google.com

Document hash

954ee84118d6983fc0a4a7fa1054203106aae0bd302b92d7990b3a040dc45fe3

Script hashes

  • fea12980cde1c3fedcabed149ba9b29ecd884868564989b56502f17c0620e4a5

TLS session and certificate

Subject alternative names
  • *.github.com
  • *.github.io
  • *.githubusercontent.com
  • github.com
  • github.io
  • githubusercontent.com
Cipher
AES_128_GCM
Issuer
YR1
Subject
*.github.io
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

1

Registered domain age, days

1

Certificate age, days

30

Certificate validity, days

89

Page requests

9

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
99
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • instagram
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Instagram
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
GitHub.com
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31556952
Original source fields · JSON
Uuid
01a1941c-dab7-710a-9f21-2acb30bfc041
Final url
https://law993.github.io/123/
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://law993.github.io/123",
        "from": "http://law993.github.io/123",
        "status": 307
    },
    {
        "to": "https://law993.github.io/123/",
        "from": "https://law993.github.io/123",
        "status": 301
    }
]
Ip
2606:50c0:8002::153
Contacted domains
[
    "cdnjs.cloudflare.com"
]
Contacted IP addresses
[
    "104.17.25.14",
    "2606:50c0:8002::153"
]
Asns
[
    "13335",
    "54113"
]
Countries
[
    "US"
]
Linked domains
[
    "apps.apple.com",
    "play.google.com"
]
Document hash
954ee84118d6983fc0a4a7fa1054203106aae0bd302b92d7990b3a040dc45fe3
Script hashes
[
    "fea12980cde1c3fedcabed149ba9b29ecd884868564989b56502f17c0620e4a5"
]
Tls
{
    "san": [
        "*.github.com",
        "*.github.io",
        "*.githubusercontent.com",
        "github.com",
        "github.io",
        "githubusercontent.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR1",
    "subject": "*.github.io",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-29T23:44:45Z",
    "valid_from": "2026-09-30T23:44:46Z"
}
Domain age days
1
Apex age days
1
Tls age days
30
Tls valid days
89
Requests
9
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "instagram"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Instagram"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "GitHub.com",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31556952"
}
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
01a1941c-dab7-710a-9f21-2acb30bfc041
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

da384e88-e231-4526-ac05-ed27e63b1404

Final URL

https://law993.github.io/

HTTP response

404

Navigation history

  • URL
    https://law993.github.io/
    Status
    404

DOM structure hash

35bbdd99a249decabdc93f6b809b030db834533d4d78fe69529a214489fae670

Document hash

70d613e3acfba24fd2876fcbacaf639e1e111ef4d54baf70761c47673f37d6a3

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    law993.github.io
    Type
    A
    Value
    185.199.108.153
  • Name
    law993.github.io
    Type
    A
    Value
    185.199.110.153
  • Name
    law993.github.io
    Type
    A
    Value
    185.199.111.153
  • Name
    law993.github.io
    Type
    A
    Value
    185.199.109.153
  • Name
    law993.github.io
    Type
    AAAA
    Value
    2606:50c0:8002::153
  • Name
    law993.github.io
    Type
    AAAA
    Value
    2606:50c0:8001::153
  • Name
    law993.github.io
    Type
    AAAA
    Value
    2606:50c0:8003::153
  • Name
    law993.github.io
    Type
    AAAA
    Value
    2606:50c0:8000::153

DNSSEC valid

No

IP address

127.0.1.11

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

Registration record

Registrar
MarkMonitor Inc.
Registered
Updated
Expires
Nameservers
  • ns-692.awsdns-22.net
  • ns-1622.awsdns-10.co.uk
  • dns1.p05.nsone.net
  • dns2.p05.nsone.net
  • dns3.p05.nsone.net
Original source fields · JSON
Uuid
da384e88-e231-4526-ac05-ed27e63b1404
Final url
https://law993.github.io/
Status
404
History
[
    {
        "url": "https://law993.github.io/",
        "status": 404
    }
]
DOM structure hash
35bbdd99a249decabdc93f6b809b030db834533d4d78fe69529a214489fae670
Document hash
70d613e3acfba24fd2876fcbacaf639e1e111ef4d54baf70761c47673f37d6a3
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "law993.github.io",
        "type": "A",
        "value": "185.199.108.153"
    },
    {
        "name": "law993.github.io",
        "type": "A",
        "value": "185.199.110.153"
    },
    {
        "name": "law993.github.io",
        "type": "A",
        "value": "185.199.111.153"
    },
    {
        "name": "law993.github.io",
        "type": "A",
        "value": "185.199.109.153"
    },
    {
        "name": "law993.github.io",
        "type": "AAAA",
        "value": "2606:50c0:8002::153"
    },
    {
        "name": "law993.github.io",
        "type": "AAAA",
        "value": "2606:50c0:8001::153"
    },
    {
        "name": "law993.github.io",
        "type": "AAAA",
        "value": "2606:50c0:8003::153"
    },
    {
        "name": "law993.github.io",
        "type": "AAAA",
        "value": "2606:50c0:8000::153"
    }
]
Dnssec valid
false
Ip
127.0.1.11

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

Registration record
{
    "registrar": "MarkMonitor Inc.",
    "created": "2013-03-08T19:12:48Z",
    "updated": "2026-08-12T09:08:04Z",
    "expires": "2027-03-08T19:12:48Z",
    "nameservers": [
        "ns-692.awsdns-22.net",
        "ns-1622.awsdns-10.co.uk",
        "dns1.p05.nsone.net",
        "dns2.p05.nsone.net",
        "dns3.p05.nsone.net"
    ]
}

Google Safe Browsing

No threat flag

Open report

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
law993.github.io GitHub Pages 404 Error Page
ai_description
PhishDestroy describes law993.github.io, a GitHub Pages 404 error page stating that no site exists at this address.
ai_summary
The captured page at law993.github.io is a GitHub Pages 404 error page, displaying a large "404" heading and the message "There isn't a GitHub Pages site here." Below that, it offers a link to read the full documentation on setting up GitHub Pages for a repository, organization, or user account, along with links to GitHub Status and @githubstatus. The page contains no login form or credential fields, and the only interaction offered is following the documentation link. The stored VirusTotal domain result reports 9 detections out of 92 engines. DNS8 reported "suspicious"; G-Data reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 00:19:40
revision
6ef96cc9af540f632a0c0c1c9545b31637a26ca1905fdfac7ffce21d9125af8e
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: 14 fields

Mail configuration

SPF lookups
0

CAA records

Count
6
Domain
law993.github.io
Allowed issuers
  • digicert.com
  • letsencrypt.org
  • sectigo.com

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

TLS connection

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

Ports

Open ports
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    198.51.45.5
    Host
    dns2.p05.nsone.net
  • IP address
    198.51.45.69
    Host
    dns4.p05.nsone.net
  • IP address
    205.251.197.59
    Host
    ns-1339.awsdns-39.org
  • IP address
    205.251.198.86
    Host
    ns-1622.awsdns-10.co.uk
  • IP address
    198.51.44.69
    Host
    dns3.p05.nsone.net
  • IP address
    205.251.194.180
    Host
    ns-692.awsdns-22.net
  • IP address
    205.251.193.137
    Host
    ns-393.awsdns-49.com
  • IP address
    198.51.44.5
    Host
    dns1.p05.nsone.net
DNS zone
github.io

Location

IP address
2606:50c0:8003::153
ASN
54113
Organization
Fastly, Inc.
Country
US

TLS certificate

Issuer
Let's Encrypt / YR1
Subject
*.github.io

DNS records

A
  • 185.199.111.153
  • 185.199.108.153
  • 185.199.110.153
  • 185.199.109.153
AAAA
  • 2606:50c0:8002::153
  • 2606:50c0:8003::153
  • 2606:50c0:8000::153
  • 2606:50c0:8001::153

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
default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2606:50c0:8001::153
IP version
6

HTTP headers

Response headers
Server
GitHub.com
Content-type
text/html; charset=utf-8
Content-security-policy
default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 6,
    "domain": "law993.github.io",
    "issuers": [
        "digicert.com",
        "letsencrypt.org",
        "sectigo.com"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "198.51.45.5",
            "host": "dns2.p05.nsone.net"
        },
        {
            "ip": "198.51.45.69",
            "host": "dns4.p05.nsone.net"
        },
        {
            "ip": "205.251.197.59",
            "host": "ns-1339.awsdns-39.org"
        },
        {
            "ip": "205.251.198.86",
            "host": "ns-1622.awsdns-10.co.uk"
        },
        {
            "ip": "198.51.44.69",
            "host": "dns3.p05.nsone.net"
        },
        {
            "ip": "205.251.194.180",
            "host": "ns-692.awsdns-22.net"
        },
        {
            "ip": "205.251.193.137",
            "host": "ns-393.awsdns-49.com"
        },
        {
            "ip": "198.51.44.5",
            "host": "dns1.p05.nsone.net"
        }
    ],
    "zone": "github.io"
}
Location
{
    "ip": "2606:50c0:8003::153",
    "asn": "54113",
    "org": "Fastly, Inc.",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YR1",
    "subject": "*.github.io"
}
DNS records
{
    "A": [
        "185.199.111.153",
        "185.199.108.153",
        "185.199.110.153",
        "185.199.109.153"
    ],
    "AAAA": [
        "2606:50c0:8002::153",
        "2606:50c0:8003::153",
        "2606:50c0:8000::153",
        "2606:50c0:8001::153"
    ]
}
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": "default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'",
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "2606:50c0:8001::153",
    "family": 6
}
HTTP headers
{
    "headers": {
        "server": "GitHub.com",
        "content-type": "text/html; charset=utf-8",
        "content-security-policy": "default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'"
    }
}

Questions about law993.github.io

Is law993.github.io legit?

PhishDestroy describes law993.github.io, a GitHub Pages 404 error page stating that no site exists at this address.

Is law993.github.io safe to connect a wallet?

This report does not record which wallet requests law993.github.io 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 law993.github.io?

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 · PhishFeed · no match in the other 10 2
PhishDestroy PhishDestroy list View source
PhishFeed Listed View source

Checked, no match

Last checked

Stored Capture · 7 captures

Cloudflare Radar 1 / 7 Used in the analysis Source file SHA-256: 044f029a882364cc282e02c3464dd54f7194cb3d9574cdef689adf7722f5c774 SHA-256 of the prepared copy given to the model: 4d2cca2254d042525b5c96cf065f674cb0da9945ee2b5f71c6814da7868622cc
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status404
Final URLhttps://law993.github.io/
Position1 / 7
Open capture Source Report Wayback Download
All capture links and hashes (7)

Domain details

Domain
IP Context United States185.199.108.153 Fastly shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider GitHub
Abuse contactabuse@github.com
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
Submitted URLhttp://law993.github.io/123
TLS Certificate
Issued by Let's Encrypt / YR1 · stored validity ends in 59 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States185.199.108.153
Network ASN
AS54113
Organization
Fastly, Inc.
Observed location
United StatesSan Francisco, US
Server header
GitHub.com

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR1
Valid from
2026-09-30 23:44:46
Valid until
2026-12-29 23:44:45
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintf2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856
Certificate names · 6 SANs
  • *.github.com
  • *.github.io
  • *.githubusercontent.com
  • github.com
  • github.io
  • githubusercontent.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 · 185.199.108.153rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

9 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 9 detections
alphaMountain.ai
DNS8
Emsisoft
Fortinet
G-Data
Netcraft
SOCRadar
Sophos
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of law993.github.io · checked Oct 31, 2026

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

Captured network requests

Network requests: 9 SHA-256 hashes: 9 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-31 22:44 UTC.

Open this scan on URLScan 01a1941c-dab7-710a-9f21-2acb30bfc041 ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

All retained availability observations2

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_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-31 23:39:42.000000
    Evidence SHA-256
    28aa235e64635e6fb03b88199ca6da68387bebade3543ffb8dbf6d66c502a5c8
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:39:42
    Evidence reason
  2. 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-31 23:39:42.000000
    Evidence SHA-256
    28aa235e64635e6fb03b88199ca6da68387bebade3543ffb8dbf6d66c502a5c8
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:39:42
    Evidence reason

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · recorded

Recorded events: 8. 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
    law993.github.io detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Blocklist Detection · Forensic Evidence Collected Recorded: 6 of 6
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • 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.
  • VirusTotal
    Detections recorded on VirusTotal: 9/92
  • Blocklist Detection
    Found in blocklists: PhishFeed
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

3 entries
  1. Added to PhishDestroy

    law993.github.io

    View source
  2. URLScan

    Page captured

    View source
  3. VirusTotal

    9/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

Check for cloaking

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

law993.github.io

Evidence & External Reports

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

Were You Affected by This Site?

3 evidence signal groups linked Server error
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 law993.github.io)
  • 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/law993.github.io"
  title="PhishDestroy threat report for law993.github.io"
  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>