Skip to content

Hostname

opayweb.com

Last fetched

opayweb.com resolves to 159.138.174.1, announced in 159.138.160.0/20 by HWCLOUDS-AS-AP - HUAWEI CLOUDS in ZA. opayweb.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · opayweb.comRouting diversity1.5/10Peering density7.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/opayweb.com

Resolution chain

IPv6 resolution

No AAAA record for opayweb.com is recorded in WhisperGraph.

Attribution

huawei international pte

ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of opayweb.com owner
Contact emails
24251140-1b83-449e-9329-ada6f6ccff17@identity-protect.org, 2635c97c-8535-4f29-82c6-bcb2cd1a59ac@identity-protect.org, 462941fc-007b-45d2-939b-b860938c7619@identity-protect.org, 4f942747-9fb3-460c-9a09-6ea6a72ce242@identity-protect.org, 766c1bb3-2086-40c0-941c-73391423c822@identity-protect.org, 89f11e22-40d5-49b4-81c2-4c3299496f61@identity-protect.org, c52b1104-f656-4ef6-a0e9-0450ef642858@identity-protect.org, owner-3269913@opayweb.com.whoisprivacyservice.org, owner-4017599@opayweb.com.whoisprivacyservice.org, owner-6524710@opayweb.com.whoisprivacyservice.org, owner-8154810@opayweb.com.whoisprivacyservice.org

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns-471.awsdns-58.com
  • ns-769.awsdns-32.net
  • ns-1493.awsdns-58.org
  • ns-1670.awsdns-16.co.uk

MX records

  • mx1.sg.aliyun.com
  • mx2.sg.aliyun.com

Threat-feed evidence

History

Related pages

Pivot from opayweb.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "opayweb.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.