Hostname
perf-hapicen.com
Last fetched
perf-hapicen.com resolves to 100.50.31.108, announced in 100.48.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. perf-hapicen.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 100.50.31.108
100.48.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 100.50.71.227
100.48.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.215.101.177
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.195.134.105
34.192.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.195.51.40
34.192.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 35.168.109.50
35.168.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 35.174.130.83
35.168.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.146.0.20
54.144.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.157.193.63
54.156.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.82.65.189
54.80.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for perf-hapicen.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of perf-hapicen.com owner
- Contact emails
- 04f58e06-e2ee-4b6d-9006-230b637f08ca@identity-protect.org, 4a09202c-b71b-4742-8317-becb1110aff7@identity-protect.org, 90c1d48b-0c30-42dc-8c5d-0f58ac5c24b1@identity-protect.org, 9eb40358-68b3-4eaa-b71b-0e0d9f061707@identity-protect.org, ce4712ea-6ae7-4a60-ae25-8a7f66e6dd79@identity-protect.org, d3446488-8f0c-4c8c-9d8e-d62fbe593c72@identity-protect.org, owner-6883726@perf-hapicen.com.whoisprivacyservice.org
Mail and authentication
Nameservers
- ns-396.awsdns-49.com
- ns-1003.awsdns-61.net
- ns-1376.awsdns-44.org
- ns-1712.awsdns-22.co.uk
Threat-feed evidence
History
Related pages
Pivot from perf-hapicen.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: "perf-hapicen.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.