Hostname
fastel.ph
Last fetched
fastel.ph resolves to 198.187.29.180, announced in 198.187.29.0/24 by NAMECHEAP-NET - Namecheap, Inc. in US. fastel.ph is listed by 1 threat feed; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 1 threat feed. At least one source recommends blocking.
Categories: Phishing
- Threat feeds listing this
- 1
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:49:49 GMT
- Last seen on a feed
- Thu, 17 Sep 2026 20:06:36 GMT
Nutrition Label
Resolution chain
- 198.187.29.180
198.187.29.0/24 · NAMECHEAP-NET - Namecheap, Inc. · Dallas, US
- 172.239.48.136
172.239.32.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.238.172.68
172.238.160.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.239.193.190
172.239.192.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
IPv6 resolution
No AAAA record for fastel.ph is recorded in WhisperGraph.
Attribution
namecheap
ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for fastel.ph. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Subdomains
Mail and authentication
Nameservers
- ns1.parklogic.com
- ns2.parklogic.com
- ns1.zainph.com
- ns2.zainph.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- mx156.hostedmxserver.com
- mail.fastel.ph
SPF policy
- include: spf.hosting.registrar-servers.com
- a: fastel.ph
- mx: fastel.ph
- ip: 198.187.29.174
- ip: 198.187.29.179
- ip: 198.187.29.180
- ip: 198.187.29.216
Threat-feed evidence
History
Related pages
Pivot from fastel.ph 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: "fastel.ph"})-[: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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.