Skip to content

Hostname

fasspay.com

Last fetched

fasspay.com resolves to 211.25.231.167, announced in 211.25.0.0/16 by TTNET-MY - TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, Malaysia in MY. fasspay.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 · fasspay.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/fasspay.com

Resolution chain

IPv6 resolution

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

Attribution

tt dotcom sdn bhd

ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,
Contact emails
fasspay.com@domainsbyproxy.com

Subdomains

Subdomain
acquiring.fasspay.com
aeon-posh-my.fasspay.com
aeon-uat.fasspay.com
aeon.fasspay.com
airasia-wallet-my.fasspay.com
azurezebrauat.fasspay.com
beta.fasspay.com
biz.fasspay.com
cba-api-syd-uat.fasspay.com
cba-posh-au.fasspay.com
cpanel.fasspay.com
cpcalendars.fasspay.com

Showing 12 of 57. View all subdomains →

Web-graph footprint

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

Sample inbound links

Mail and authentication

Nameservers

  • ns-401.awsdns-50.com
  • ns-635.awsdns-15.net
  • ns-1130.awsdns-13.org
  • ns-1611.awsdns-09.co.uk

MX records

  • fasspay-com.mail.protection.outlook.com

SPF policy

  • ip: 103.6.198.21/15
  • include: amazonses.com
  • a: fasspay.com
  • mx: fasspay.com
  • include: _spf.google.com
  • include: spf.protection.outlook.com
  • ip: 110.4.45.198

Threat-feed evidence

History

Related pages

Pivot from fasspay.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: "fasspay.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.