Hostname
com-finance.com
Last fetched
com-finance.com resolves to 15.197.240.20, announced in 15.197.240.0/20 by AMAZON-02 - Amazon.com, Inc. in CA. com-finance.com 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.
- Threat feeds listing this
- 1
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:49:47 GMT
- Last seen on a feed
- Mon, 21 Sep 2026 23:09:40 GMT
Nutrition Label
Resolution chain
- 15.197.240.20
15.197.240.0/20 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
- 160.251.64.80
160.251.64.0/20 · GMO-I-R1 - GMO Internet, Inc. · Chiyoda, JP
- 195.201.128.179
195.201.0.0/16 · HETZNER-AS - Hetzner Online GmbH · Nuremberg, DE
- 46.62.237.138
46.62.128.0/17 · HETZNER-AS - Hetzner Online GmbH · Helsinki, FI
- 5.161.230.87
5.161.230.0/24 · HETZNER-CLOUD2-AS - Hetzner Online GmbH · Ashburn, US
- 5.161.47.86
5.161.47.0/24 · HETZNER-CLOUD2-AS - Hetzner Online GmbH · Ashburn, US
- 5.78.156.59
5.78.156.0/24 · HETZNER-CLOUD3-AS - Hetzner Online GmbH · Hillsboro, US
- 76.223.91.20
76.223.80.0/20 · AMAZON-02 - Amazon.com, Inc. · Seattle, US
IPv6 resolution
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:49
- Registrant organisation
- custom names
- Contact emails
- com-finance.com@whoisprotectservice.net, domains@companyname.net, contact@privacyprotect.org
Mail and authentication
Nameservers
- ns1.dns-redirect.com
- ns2.dns-redirect.com
- dns1.onamae-expired.com
- dns2.onamae-expired.com
- ns1.verification-hold.suspended-domain.com
- ns2.verification-hold.suspended-domain.com
- a.gtld-servers.net
- b.gtld-servers.net
- c.gtld-servers.net
- d.gtld-servers.net
- e.gtld-servers.net
- f.gtld-servers.net
- g.gtld-servers.net
- h.gtld-servers.net
- i.gtld-servers.net
- j.gtld-servers.net
- k.gtld-servers.net
- l.gtld-servers.net
- m.gtld-servers.net
Threat-feed evidence
History
Related pages
Pivot from com-finance.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: "com-finance.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.